Re: [GUILT v2 00/29] Teach guilt import-commit how to create legal patch names, and more
- From
- Jeff Sipek <jeffpc@josefsipek.net>
- Date
- May 13, 2014, 20:54 UTC
- Message-ID
- <20140513205443.GB4791@meili.valhalla.31bits.net>
- In-Reply-To
- <20140513204546.GB11391@thunk.org>
On Tue, May 13, 2014 at 04:45:47PM -0400, Theodore Ts'o wrote:
> On Tue, May 13, 2014 at 10:30:36PM +0200, Per Cederqvist wrote:
...
Show 9 quoted lines
> > - Changed behavior: by default, guilt no longer changes branch when > > you push a patch. You need to do "git config guilt.reusebranch > > false" to re-enable that. This patch sets the default value of > > guilt.reusebranch to true; it should in my opinion change to false > > a year or two after the next release. > > We've been living with the "origin" -> "guilt/origin" branch change > for a year already, and in fact, these days I've gotten used to the > new behavior. Is it really worth it to change the default?
So, at first I was skeptical about the branch name prefix change. I've used it for about a year now, and I love it. When I first read Per's idea to change the default to the old-style, I was a bit sad but I understand the motivation.
I'm open to either mode being the default since it's easy enough for me to change it for me (thanks, ~/.gitconfig) but I think more people should benefit from the added safety against accidental git-push. (I also like being able to use guilt/master..master to get only the commits I care about.) Thoughts?
Jeff.
-- Intellectuals solve problems; geniuses prevent them - Albert Einstein