Le ven 12/09/2003 � 12:45, Sven Luther a �crit : > > [...] > > But you haven't covered the very serious issue here: sarge can't even ship > > as is. Why the temptation to introduce even more problems (the possibility > > of 2.4 piecemeal migrating) instead of ensuring a shippable sarge by letting > > 2.2 migrate down completely? > > As said in another mail. Why not upload the missing piece of 2.2 to > testing-proposed-updates (provided they are not buggy per see, just hold > up by glibc and co) and then go forward by uploading 2.4 to sid, and > making sure the 2.4 will not enter sarge until we think it ready by > filling bogus bug report or something such. >
I like this idea. But I don't know if the RM will accept it, because there are lots of package to migrate. -- C�dric Delfosse, http://cedric.freezope.org Jabber ID: [EMAIL PROTECTED]
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
