public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benjamin Judas <beejay@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] ChangeLog for 2004.3 ***NEW AND IMPROVED***
Date: Sat, 06 Nov 2004 13:42:13 +0100	[thread overview]
Message-ID: <1099744933.20532.15.camel@antares.hausnetz> (raw)
In-Reply-To: <1099744699.20532.11.camel@antares.hausnetz>

[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]

Am Samstag, den 06.11.2004, 13:38 +0100 schrieb Benjamin Judas:
> Am Samstag, den 06.11.2004, 12:00 +0100 schrieb Gregorio Guidi:
> > On Saturday 06 November 2004 11:42, Benjamin Judas wrote:
> > > Am Freitag, den 05.11.2004, 16:58 -0500 schrieb Chris Gianelloni:
> > > > Umm... guys... come on... give me something to work with... after all,
> > > > the information here will probably end up in the press release and will
> > > > also make it into loads of articles, so now is the time to puff up your
> > > > chest and be proud of all the hard work you've done.
> > >
> > > http://www.gentoo.org/proj/en/releng/release/2004.3/x86-release-notes.xml
> > >
> > > Everything that has changed / that is new is already written there:
> > > what Versions of gcc and glibc, that we switched to cascading-profiles etc.
> > 
> > I see the release notes already include a link to 
> > http://www.gentoo.org/doc/en/gentoo-upgrading.xml
> > about cascading profiles.
> > What about linking that guide also in the 'Upgrading to Gentoo Linux 2004.3' 
> > section, to substitute the information there? It is quite outdated now.
> > 
> > Thanks
> > Gregorio Guidi
> > 
> > --
> > gentoo-releng@gentoo.org mailing list
> > 
> 
> Maybe you have overseen it, but it is linked.

Sorry, sorry, sorry.

Well, if somebody already has an installation using a 2004.2-profile, he
will be noticed by portage about the change, so I think there's no need
to include that information in the upgrading part again. If he does what
is described there, he will be notified about the profile being
deprecated and be told how to upgrade.

Regards,


-- 

Benjamin Judas

---------------------------------------------------------------------                                  
Gentoo-developer                        http://dev.gentoo.org/~beejay
Giessen, Germany                                http://www.gentoo.org

GPG-Key         : 0xC31DEDD8
Key-Fingerprint : 4E65 AAFE 785B 61D8 E4D9  1671 E017 87B7 C31D EDD8
Jabber          : beejay@im.gentoo.org



[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-06 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 15:36 [gentoo-releng] ChangeLog for 2004.3 ***NEW AND IMPROVED*** Chris Gianelloni
2004-11-05 21:58 ` Chris Gianelloni
2004-11-06 10:42   ` Benjamin Judas
2004-11-06 11:00     ` Gregorio Guidi
2004-11-06 12:38       ` Benjamin Judas
2004-11-06 12:42         ` Benjamin Judas [this message]
2004-11-07  3:41   ` [gentoo-releng] PPC 2004.3 ChangeLog Pieter Van den Abeele
2004-11-14 21:53 ` [gentoo-releng] ChangeLog for 2004.3 ***NEW AND IMPROVED*** Jason Huebel

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=1099744933.20532.15.camel@antares.hausnetz \
    --to=beejay@gentoo.org \
    --cc=gentoo-releng@lists.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