From: Jay Goodman Tamboli <jay@tamboli.cx>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] drobbins mass mark stable
Date: Sat, 21 Jun 2003 20:44:42 -0400 [thread overview]
Message-ID: <20030622004442.GA27796@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
I just did a sync (server scrolled offscreen. logged
anywhere?), and I notice lots of upgrades, including glibc
to 2.3.2-r1 (from 2.3.1-r4). I started checking some of the
CVS logs, and at least for glibc, man, and fileutils, the
change of KEYWORD ~x86 to x86 was done by drobbins as part
of "amd64" fixes. I'd like to be careful about a glibc
upgrade, so can someone confirm that all these changes are
intentional and correct?
/jgt
--
I would sooner fail than not be among the greatest. -- John Keats
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-06-22 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 0:44 Jay Goodman Tamboli [this message]
2003-06-22 0:47 ` [gentoo-dev] drobbins mass mark stable Jon Portnoy
2003-06-22 0:49 ` Jon Portnoy
2003-06-22 0:53 ` John Mylchreest
2003-06-22 16:51 ` Marius Mauch
2003-06-22 18:06 ` Jon Portnoy
2003-06-22 16:11 ` Alan
2003-06-22 0:52 ` John Mylchreest
2003-06-22 10:23 ` FRLinux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030622004442.GA27796@localhost.localdomain \
--to=jay@tamboli.cx \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox