Re: posix_fallocate behavior in glibc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Cristian Rodríguez <cristian@xxxxxxxxxxxx>
Subject: Re: posix_fallocate behavior in glibc
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 29 Jul 2024 20:45:01 +0200
Cc: Christoph Hellwig <hch@xxxxxx>, Paul Eggert <eggert@xxxxxxxxxxx>, Trond Myklebust <trondmy@xxxxxxxxxxxxxxx>, libc-alpha@xxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <CAPBLoAf11hM0PLhqPG5gUyivU9U1manpOOhDWCPugUmWc1VVUw@mail.gmail.com>
User-agent: Mutt/1.5.17 (2007-11-01)

On Mon, Jul 29, 2024 at 02:40:00PM -0400, Cristian Rodríguez wrote:
> Do you mean glibc copyright assigment ? DCO is now ok.

Oh, I completely missed that.  Thanks or the headsup.

References:
- posix_fallocate behavior in glibc
  - From: Christoph Hellwig
- Re: posix_fallocate behavior in glibc
  - From: Paul Eggert
- Re: posix_fallocate behavior in glibc
  - From: Christoph Hellwig

Prev by Date: Re: posix_fallocate behavior in glibc
Next by Date: Re: posix_fallocate behavior in glibc
Previous by thread: Re: posix_fallocate behavior in glibc
Next by thread: Re: posix_fallocate behavior in glibc
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux