From: Jason Wever <weeve@gentoo.org>
To: Gentoo Dev Mailing List <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS
Date: Tue, 24 Aug 2004 21:00:50 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0408242100120.31215@stargazer.weeve.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0408241907500.31215@stargazer.weeve.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 24 Aug 2004, Jason Wever wrote:
> Is there a written policy anyway for the behavior of carrying KEYWORDS
> over from one version of an ebuild for a given package to another?
Ciaranm set me straight on this, so no replies necessary :)
Man does my head hurt though,
- --
Jason Wever
Gentoo/Sparc Co-Team Lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBLADkdKvgdVioq28RAlkfAJ4rqTHsk59LjT+Z65qGqnIW1MTVegCcCF/T
hG1R4j2Qcd9sVndrXc7hNw0=
=X+Cl
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-08-25 3:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 1:11 [gentoo-dev] Ebuild bumping policy wrt KEYWORDS Jason Wever
2004-08-25 3:00 ` Jason Wever [this message]
2004-08-25 15:30 ` Michael Kohl
2004-08-26 3:17 ` Jason Wever
2004-08-26 14:51 ` Carsten Lohrke
2004-08-26 15:04 ` Ciaran McCreesh
2004-08-26 15:30 ` Carsten Lohrke
2004-08-26 15:33 ` Ciaran McCreesh
2004-08-26 16:11 ` Travis Tilley
2004-08-31 13:07 ` foser
2004-09-01 2:09 ` Travis Tilley
2004-09-01 10:06 ` foser
2004-09-01 16:30 ` Robert Moss
2004-09-01 23:15 ` Carsten Lohrke
2004-09-01 23:20 ` Ciaran McCreesh
2004-09-01 23:42 ` Carsten Lohrke
2004-08-26 16:27 ` Carsten Lohrke
2004-08-31 13:23 ` foser
2004-08-25 13:51 ` Chris Gianelloni
2004-08-26 3:22 ` Jason Wever
2004-08-26 4:49 ` Donnie Berkholz
2004-08-26 5:20 ` Jason Wever
2004-08-26 6:19 ` Donnie Berkholz
2004-08-26 14:16 ` Chris Gianelloni
2004-08-26 14:44 ` Ciaran McCreesh
2004-08-26 15:02 ` Chris Gianelloni
2004-08-26 15:31 ` Jason Wever
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=Pine.LNX.4.61.0408242100120.31215@stargazer.weeve.org \
--to=weeve@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