bug-grep
[Top][All Lists]
Advanced

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

Re: --with-included-foo={yes,no} and which foo.h to use?


From: Aharon Robbins
Subject: Re: --with-included-foo={yes,no} and which foo.h to use?
Date: Thu, 07 Jul 2005 11:25:40 +0300

> Date: Thu, 07 Jul 2005 02:33:59 -0400
> From: Charles Levert <address@hidden>
> Subject: Re: --with-included-foo={yes,no} and which foo.h to use?
> To: address@hidden
>
> Updating to glibc's regex.c will allow us to
> progress in fixing RE_ICASE bugs now, and maybe
> others as well.  That why I can't see one being
> a priority without the other.

I think it's a good idea. Call the next release 2.6 if you must, but
moving off the old regex is very important IMHO.

> The following ChangeLog entry lists files that
> do not appear in the diff output below, either
> because they are completely new and untouched,
> or because the main lib/regex.c diff is huge
> and irrelevant.

One thing I've started doing in gawk, just for my own sanity, is putting
the CVS/RCS $Id$ numbers of glibc files into the ChangeLog when I import
them.  That way, a year later I know what version I started with and I
can look at the current glibc to see what's changed.  That also makes
it easier to see which, if any, of my changes may have filtered back
into glibc, so that I don't need to propogate them forward.

So, I recommend that practice for grep as well.

HTH,

Arnold




reply via email to

[Prev in Thread] Current Thread [Next in Thread]