Re: Example where testing-security was used?
- To: debian-devel@lists.debian.org
- Subject: Re: Example where testing-security was used?
- From: Alexander Schmehl <alexander@schmehl.info>
- Date: Wed, 1 Jun 2005 18:31:53 +0200
- Message-id: <[🔎] 20050601163153.GC9304@schmehl.info>
- Mail-followup-to: debian-devel@lists.debian.org
- In-reply-to: <87ll5vtsiy.fsf@orebokech.com>
- References: <20050523031035.GQ23219@mauritius.dodds.net> <20050530103421.GA10441@stusta.de> <20050530104854.GA22643@sirena.org.uk> <20050530124838.GE24763@cloud.net.au> <8764x0cu1b.fsf@nahar.localdomain> <20050531092539.GS3627@stusta.de> <20050531115652.GA23271@mauritius.dodds.net> <20050531120148.GW3627@stusta.de> <20050531125021.GG23271@mauritius.dodds.net> <87ll5vtsiy.fsf@orebokech.com>
* Romain Francoise <rfrancoise@debian.org> [050531 15:49]:
> Speaking of prospective ports, what would be the feasibility of keeping
> testing frozen after sarge releases, do whatever toolchain updates are
> needed to support amd64 via t-p-u, and release etch as a "sarge+amd64"
> release in, say, 3 months?
http://www.nl.debian.org/vote/2004/vote_004
http://www.nl.debian.org/vote/2004/vote_003
I can hardly imagine, you can fix all that in three month.
Yours sincerely,
Alexander
--
http://learn.to/quote/
http://www.catb.org/~esr/faqs/smart-questions.html
Attachment:
signature.asc
Description: Digital signature
Reply to: