Eric Blake wrote:
> According to Reuben Thomas on 3/17/2009 5:53 PM:
>> On Tue, 17 Mar 2009, Jim Meyering wrote:
>>
>>> Thanks. That sounds like a fine improvement.
>>> Do you feel like writing a commit-log/ChangeLog entry, too?
>>> (i.e., git format-patch output, per e.g.,
>>> http://git.sv.gnu.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Reuben Thomas on 3/17/2009 6:36 PM:
> On Tue, 17 Mar 2009, Eric Blake wrote:
>
>> In the meantime, I did a search of the copyright assignments; I see that
>> you have assignment on file for coreutuils, but not gnulib. Since it
>> is a
>>
On Tue, 17 Mar 2009, Eric Blake wrote:
In the meantime, I did a search of the copyright assignments; I see that
you have assignment on file for coreutuils, but not gnulib. Since it is a
separate project, I'd recommend repeating the process to ensure your
future gnulib contributions are not a pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Reuben Thomas on 3/17/2009 5:53 PM:
> On Tue, 17 Mar 2009, Jim Meyering wrote:
>
>> Thanks. That sounds like a fine improvement.
>> Do you feel like writing a commit-log/ChangeLog entry, too?
>> (i.e., git format-patch output, per e.g.,
On Tue, 17 Mar 2009, Jim Meyering wrote:
Thanks. That sounds like a fine improvement.
Do you feel like writing a commit-log/ChangeLog entry, too?
(i.e., git format-patch output, per e.g.,
http://git.sv.gnu.org/cgit/coreutils.git/plain/HACKING)
Attached; since I haven't done this before, let
Reuben Thomas wrote:
> The documentation says:
>
> --without-included-regex
> don't compile regex; this is the default on 32-bit
> systems with recent-enough versions of the GNU C
> Library (use with caution on other sy
The documentation says:
--without-included-regex
don't compile regex; this is the default on 32-bit
systems with recent-enough versions of the GNU C
Library (use with caution on other systems). On
