From: Jason Wever <weeve@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: [gentoo-dev] Please follow keywording policy
Date: Tue, 8 Mar 2005 18:55:36 -0700 [thread overview]
Message-ID: <20050308185536.58ecbe3c@enterprise.weeve.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
Hi All,
I'd like to ask that you all take the time to review the keywording
policy in the Developer Handbook. In particular, I'd like to draw
your attention to the section on "Upgrading Ebuilds" [1].
People have been getting good lately at either dropping keywords for
no reason and/or failing to notify or file a bug with the arches
dropped as to why. Chances are if you have done this for SPARC, you've
probably heard from me already. If not, GenBot is on his way to your
location as we speak ;)
Now back to your regularly scheduled hack-fu...
[1] -
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=5#doc_chap5
Thanks,
--
Jason Wever
Gentoo/Sparc Team Co-Lead
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-03-09 1:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 1:55 Jason Wever [this message]
2005-03-09 2:00 ` [gentoo-dev] Please follow keywording policy Hasan Khalil
2005-03-09 7:38 ` Alin Nastac
2005-03-09 13:39 ` Stephen P. Becker
2005-03-09 14:50 ` Alin Nastac
2005-03-09 16:22 ` Ciaran McCreesh
2005-03-09 17:38 ` Alin Nastac
2005-03-09 18:38 ` Ciaran McCreesh
2005-03-09 18:56 ` Alin Nastac
2005-03-09 19:10 ` Stefan Schweizer
2005-03-09 19:10 ` Stefan Schweizer
2005-03-09 21:30 ` Luis F. Araujo
2005-03-09 22:57 ` Alin Nastac
2005-03-09 23:27 ` Stephen P. Becker
2005-03-10 0:50 ` Donnie Berkholz
2005-03-10 0:18 ` Daniel Goller
2005-03-09 23:36 ` Jason Wever
2005-03-09 23:42 ` Aron Griffis
2005-03-10 7:54 ` Alin Nastac
2005-03-10 8:27 ` Ciaran McCreesh
2005-03-10 15:54 ` Chris Gianelloni
2005-03-10 15:52 ` Chris Gianelloni
2005-03-10 4:34 ` Grant Goodyear
2005-03-10 8:36 ` Alin Nastac
2005-03-10 13:14 ` Ciaran McCreesh
2005-03-10 16:00 ` Chris Gianelloni
2005-03-10 19:00 ` Alin Nastac
2005-03-10 19:33 ` Chris Gianelloni
2005-03-10 21:25 ` John Myers
2005-03-10 15:38 ` Chris Gianelloni
2005-03-09 19:18 ` Patrick Lauer
2005-03-09 19:43 ` Stefan Schweizer
2005-03-09 19:56 ` Patrick Lauer
2005-03-10 0:55 ` Jon Portnoy
2005-03-10 8:07 ` Alin Nastac
2005-03-09 19:20 ` Chris Gianelloni
2005-03-09 16:37 ` Stephen P. Becker
2005-03-09 16:43 ` Chris Gianelloni
2005-03-09 17:40 ` Alin Nastac
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=20050308185536.58ecbe3c@enterprise.weeve.org \
--to=weeve@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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