Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/
Date: Sun, 15 May 2016 22:56:20
Message-Id: pan$27f48$74f7129d$94a60ffc$35c93c83@cox.net
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: eclass/ by Daniel Campbell
1 Daniel Campbell posted on Sun, 15 May 2016 04:04:57 -0700 as excerpted:
2
3 > If the dev in question hasn't done that before, then it's entirely
4 > possible they *thought* they tested, or tested it *before* making some
5 > other edit and absent-mindedly committed.
6
7 Again, legacy CVS thought pattern. In git, commit != push, and it's the
8 push that's critical.
9
10 Commit all you want without testing. Just test (and fix if necessary)
11 before you push those commits up to the gentoo master repo. =:^)
12
13 (Of course, rebasing to fold the broken commit and its fix into one
14 before pushing doesn't hurt, either.)
15
16 --
17 Duncan - List replies preferred. No HTML msgs.
18 "Every nonfree program has a lord, a master --
19 and if you use the program, he is your master." Richard Stallman

Replies