Ben Collins wrote:
I agree to that confusion should not be occured especially glibc
until upstream thinks it reaches release stability level.
OK, we are going to patch 'one by one model' until 2.2.6/2.2.90
would be released with patch state marking you mentioned.
No, we are going to stay synced with glibc cvs's 2.2 branch. Check the
debian/patches/glibc-cvs.dpatch file. That's going to be synced, in
full.
Ugh, I completely misunderstand what you said.
I restate our plan: after -13, patches in debian/patches/* include
(1) Debian specific (2) only in 2.3 CVS (3) Hurd-i386 improvement
(I guess Jeff and hurd-machine are reincarnated :).
Such all patches marked why they are in debian/patches.
debian/patches/glibc-cvs.dpatch syncs the latest glibc-2-2-branch.
We effort to resolve our BTS bugs with sending to upstream CVS, surely.
Syncing 2.3 cvs is future work after 2.2.90 is released...
Thanks,
-- gotom
