Re: upstream regex

Eric Blake wrote: > According to Paolo Bonzini on 1/24/2009 6:20 AM: >>> Actually, Paolo imported some glibc fixes into gnulib within the past >>> month. However, we have had some gnulib fixes which have not been pushed >>> back to glibc. >> I see only dea6f7089df0538e8bc7971dfbdd84e523a79d2a in t

Re: upstream regex

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paolo Bonzini on 1/24/2009 6:20 AM: >> Actually, Paolo imported some glibc fixes into gnulib within the past >> month. However, we have had some gnulib fixes which have not been pushed >> back to glibc. > > I see only dea6f7089df0538e8bc

Re: upstream regex

Eric Blake wrote: > According to Bruno Haible on 1/24/2009 4:31 AM: >> glibc regex and gnulib regex are supposed to be synched (bidirectionally) >> regularly. Paul Eggert did this last time in 2006. It's quite some work >> to do this synch. Maybe it could be easier, now that we are using 'git' >> (

Re: upstream regex

> glibc regex and gnulib regex are supposed to be synched (bidirectionally) > regularly. Paul Eggert did this last time in 2006. It's quite some work > to do this synch. Maybe it could be easier, now that we are using 'git' > (using git branches)? I'll look at relevant gnulib patches. When I ask

Re: upstream regex

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 1/24/2009 4:31 AM: > > glibc regex and gnulib regex are supposed to be synched (bidirectionally) > regularly. Paul Eggert did this last time in 2006. It's quite some work > to do this synch. Maybe it could be easier, now t

Re: upstream regex

[CCing bug-gnulib. This is a reply to ] Hello Tony, > > Suggestion: Use the same logic for restrict and restrict_arr as in > > gnulib/lib/regex.h. > > What is considered the authoritative source of regex.h? Is it the glibc > sou