This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Glibc release check-list

From: "Alfred M. Szmidt" <ams at gnu dot org>
To: "Carlos O'Donell" <carlos at systemhalted dot org>
Cc: dan at codesourcery dot com, schwab at linux-m68k dot org, pasky at suse dot cz,libc-alpha at sourceware dot org, libc-ports at sourceware dot org
Date: Sun, 15 Nov 2009 11:44:40 -0500
Subject: Re: Glibc release check-list
References: <20091113142845.GS3708@machine.or.cz> <119aab440911130700y3e00672cwfa2c679de89a3eb5@mail.gmail.com> <E1N9FaZ-0008HI-A6@fencepost.gnu.org> <119aab440911140842u39c5967k9fd8a820cfce49ab@mail.gmail.com>
Reply-to: ams at gnu dot org

   Should the ports maintainers have a pow-wow to decide who gets to do
   the honours and when?

I think that ports releases should be done in sync with glibc.  Users
will become immensly confused if you have glibc-ports-2.42 that is to
be used with glibc 2.11.

Follow-Ups:
- Re: Glibc release check-list
  - From: Arkadiusz Miskiewicz

References:
- Glibc release check-list
  - From: Petr Baudis
- Re: Glibc release check-list
  - From: Carlos O'Donell
- Re: Glibc release check-list
  - From: Alfred M. Szmidt
- Re: Glibc release check-list
  - From: Carlos O'Donell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]