This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Release timelines: 2.15.1 and 2.16
> It may make sense to resurrect this stuff; at the least it might make
> merging patches back and forth easier. It's been on my list of things
> to look at.
Yes, please do. It makes things much more transparent for other libc
developers. I can help you with the details. In short, all the Fedora
changes get committed to the appropriate fedora/* branch, and then you
do 'make -C fedora various-targets-ive-forgotten' to regenerate an srpm
that you can import into pkgs git. This actually predates pkgs git and
IIRC pkgs cvs, so reworking the details probably makes sense.
> Well, I haven't owned glibc for Fedora for terribly long; however, it
> seems to me that Fedora ought to be picking up whatever the current
> official release is at the time Fedora branches for its next release.
> If a release is close (as was the case for glibc-2.15), then Fedora can
> track the glibc release branch as necessary.
I think it's worthwhile to be more coordinated than this.
That's logic for an uncoordinated upstream package.
Thanks,
Roland