Gentoo Archives: gentoo-dev

From: Ciaran McCreesh <ciaranm@g.o>
To: arj@g.o
Cc: gentoo-dev@l.g.o
Subject: [gentoo-dev] Committing straight to stable
Date: Sun, 24 Apr 2005 13:44:53
Message-Id: 20050424144444.58715f9c@snowdrop
1 Since keywording policy seems to be being ignored again... Don't *ever*
2 commit new ebuild revisions straight to stable, even if you think it's a
3 trivial fix. There are plenty of things that could go wrong even with
4 simple patches -- for example, if you accidentally included some CVS Id:
5 lines in your patch, they'll get nuked when you do the commit. And, if
6 you commit straight to stable, you end up breaking arch rather than just
7 ~arch.
9 The "all things must go through ~arch for a while first" rule is there
10 for a good reason. It's not something you can arbitrarily ignore because
11 you think you're not breaking anything...
13 --
14 Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
15 Mail : ciaranm at
16 Web :


Subject Author
Re: [gentoo-dev] Committing straight to stable Aaron Walker <ka0ttic@g.o>
Re: [gentoo-dev] Committing straight to stable Paul Waring <pwaring@×××××.com>
Re: [gentoo-dev] Committing straight to stable Anders Rune Jensen <arj@g.o>