-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 10/7/2009 11:00 AM:
> Eric Blake (4):
> areadlink, areadlink-with-size: add tests
> areadlinkat: new module
> 2009-10-07 Eric Blake
>
> + areadlinkat: new module
> + * lib/at-func.c (FUNC_FAIL): New
David Lutterkort wrote:
> would it be possible to relicense stpncpy (currently LGPL) as LGPLv2+ ?
Yes. This is possible, since lib/stpncpy.c originally came from glibc and
was not modified since the switch from LGPLv2+ to LGPLv3+ two years ago.
2009-10-21 Bruno Haible
* modules/stpnc
Hi Jim,
thanks for quick reply!
On Wednesday 21 of October 2009 21:47:59 Jim Meyering wrote:
> It fails for a very good reason.
> A changed device number may indicate an attempt to subvert the traversal,
> even though the inode number is the same.
I agree.
> > https://bugzilla.redhat.com/attach
Kamil Dudka wrote:
> the FTS module does not seem to be ready for a remount during traversal.
> As a minimal example we can take the following situation:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=501848#c20
Hi Kamil,
Thanks for the heads up.
However, ...
> Descending a directory triggers
Hello,
the FTS module does not seem to be ready for a remount during traversal.
As a minimal example we can take the following situation:
https://bugzilla.redhat.com/show_bug.cgi?id=501848#c20
Descending a directory triggers a shrinkable mount which implies a change
of the device number. However
Eric Blake wrote:
> According to Eric Blake on 10/15/2009 12:22 PM:
>> Eric Blake byu.net> writes:
>>
>>> The current state of the series is now pushed. Subsequent improvements,
>>> like utimensat, will come later.
>>
>> Here's the current state; I'll probably commit up through patch 4 within the
Hi,
would it be possible to relicense stpncpy (currently LGPL) as LGPLv2+ ?
I want to use it in Augeas, which is LGPLv2+.
David
