public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: removal of digest files from the tree
Date: Sun, 27 Jan 2008 13:01:09 +0000	[thread overview]
Message-ID: <1201438879l.2698l.0l@spike> (raw)
In-Reply-To: <479BD99A.8010408@gentoo.org> (from zmedico@gentoo.org on Sun Jan 27 01:08:42 2008)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2008.01.27 01:08, Zac Medico wrote:
> Now that the whole tree has been converted to Manifest2 format we can
> remove the old digest files from the tree so that it is pure 
> Manifest2 format [1]. Any
> users who still have a version of portage that doesn't support
> Manifest2 (less than sys-apps/portage-2.1 or stages prior to 2006.1) 
> will still be able to use a script to generate the old digests if 
> they want to upgrade an old system [2].
>
[snip]
> If there are no objections then I don't so any reason not to go ahead
> and add the manifest1_obsolete sometime in the near future. Thoughts?
> 
> Zac
> 
> [1]
> http://www.gentoo.org/proj/en/glep/glep-0044.html#removal-of-digest-
> files
> [2] http://www.gentoo.org/proj/en/portage/doc/converting-
> manifest2.xml
> 
> 

Team,

We need to get news items out, on gentoo.org, in the GWN and on the 
forums or everyone with an old portage will be unhappy. Some users will 
still be unhappy anyway but we can point to the news and say we tried 
to tell you. If link [2] will be around for a while, we can us it in an 
mzbot factoid too.

No objections ... just plenty of publicity.

- -- 
Regards,

Roy Bamford
(NeddySeagoon) a member of
gentoo-ops
forum-mods
treecleaners

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHnICfTE4/y7nJvasRAjWlAKCowpUt9i1CpdmqD7UyB6DXxzgOcQCg7+k0
t4RRbBHMuGSOhySOhmLV2II=
=PvBz
-----END PGP SIGNATURE-----

--
gentoo-dev@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-01-27 13:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27  1:08 [gentoo-dev] RFC: removal of digest files from the tree Zac Medico
2008-01-27  1:35 ` Robin H. Johnson
2008-01-27  7:30   ` Rémi Cardona
2008-01-27  9:00   ` Fabian Groffen
2008-01-27 14:06     ` Petteri Räty
2008-01-27 14:27       ` Robin H. Johnson
2008-01-27 17:52         ` Petteri Räty
2008-01-28  1:34         ` Chris Gianelloni
2008-01-28  2:01           ` Robin H. Johnson
2008-01-28  7:32             ` Chris Gianelloni
2008-01-28  8:53               ` Vlastimil Babka
2008-01-28  1:11   ` Zac Medico
2008-01-28  1:44     ` Chris Gianelloni
2008-01-28  8:56       ` Vlastimil Babka
2008-01-28 10:01       ` Gilles Dartiguelongue
2008-01-28 12:08       ` Santiago M. Mola
2008-01-30 23:05       ` Vlastimil Babka
2008-01-30 23:32         ` Robin H. Johnson
2008-01-30 23:45           ` Santiago M. Mola
2008-01-31  0:14             ` Chris Gianelloni
2008-01-31  1:00               ` Robin H. Johnson
2008-01-31 21:12                 ` Davide Cendron
2008-01-31 21:57                   ` Jan Kundrát
2008-01-31 23:09                     ` Robin H. Johnson
2008-01-28 11:07     ` Rémi Cardona
2008-01-27  1:43 ` Josh Saddler
2008-01-27 13:01 ` Roy Bamford [this message]
2008-01-28  1:43 ` Chris Gianelloni
2008-01-28  2:47   ` Zac Medico

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=1201438879l.2698l.0l@spike \
    --to=neddyseagoon@gentoo.org \
    --cc=gentoo-dev@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