Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
Marc Singer <elf@buici.com> writes:
> It does seem prudent to find a way to permit a release on x86 and
> ppc before all architectures are complete. Especially if this
> tactic will give Debian the ability to release more often. Is it so
> bad to allow the smaller architectures to lag as long as problems
> are fixed?
This would only make sense if we had a complete x86 and ppc release,
but not a complete mips release. In practical terms, this doesn't
happen. It's not like we do all the x86 work, and then the rest.
Reply to:
- References:
- [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space]
- From: Clint Byrum <cbyrum@spamaps.org>
- Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- From: Dirk Eddelbuettel <edd@debian.org>
- Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- From: Wouter Verhelst <wouter@debian.org>
- Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- From: Brian Nelson <pyro@debian.org>
- Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- From: Dirk Eddelbuettel <edd@debian.org>
- Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- From: Marc Singer <elf@buici.com>
- Prev by Date:
Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- Next by Date:
Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- Previous by thread:
Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- Next by thread:
Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
- Index(es):