From: Ciaran McCreesh <ciaranm@gentoo.org>
To: arj@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Committing straight to stable
Date: Sun, 24 Apr 2005 14:44:44 +0100 [thread overview]
Message-ID: <20050424144444.58715f9c@snowdrop> (raw)
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
Since keywording policy seems to be being ignored again... Don't *ever*
commit new ebuild revisions straight to stable, even if you think it's a
trivial fix. There are plenty of things that could go wrong even with
simple patches -- for example, if you accidentally included some CVS Id:
lines in your patch, they'll get nuked when you do the commit. And, if
you commit straight to stable, you end up breaking arch rather than just
~arch.
The "all things must go through ~arch for a while first" rule is there
for a good reason. It's not something you can arbitrarily ignore because
you think you're not breaking anything...
--
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-04-24 13:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 13:44 Ciaran McCreesh [this message]
2005-04-24 19:43 ` [gentoo-dev] Committing straight to stable Aaron Walker
2005-04-24 20:29 ` Paul Waring
2005-04-24 20:33 ` Jan Kundrát
2005-04-24 20:46 ` Paul Waring
2005-04-24 20:44 ` Ciaran McCreesh
2005-04-24 21:08 ` Francesco Riosa
2005-04-24 21:24 ` Diego 'Flameeyes' Pettenò
2005-04-24 21:35 ` Ciaran McCreesh
2005-04-24 21:37 ` Diego 'Flameeyes' Pettenò
2005-04-24 21:46 ` Ciaran McCreesh
2005-04-24 21:50 ` Alec Warner
2005-04-24 20:59 ` foser
2005-04-24 21:08 ` Paul Waring
2005-04-24 21:09 ` Ciaran McCreesh
2005-04-24 22:13 ` Mike Frysinger
2005-04-25 1:04 ` Anders Rune Jensen
2005-04-25 1:44 ` Robin H. Johnson
2005-04-25 2:04 ` Donnie Berkholz
2005-04-25 3:13 ` Robin H. Johnson
2005-04-25 4:12 ` Donnie Berkholz
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=20050424144444.58715f9c@snowdrop \
--to=ciaranm@gentoo.org \
--cc=arj@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