Re: [GUILT v2 00/29] Teach guilt import-commit how to create legal patch names, and more

[Theodore Ts'o <tytso@mit.edu>]

On Tue, May 13, 2014 at 10:30:36PM +0200, Per Cederqvist wrote:
> I recently found myself sitting on a train with a computer in front of
> me.  I tried to use "guilt import-commit", which seemed to work, but
> when I tried to "guilt push" the commits I had just imported I got
> some errors.  It turned out that "guilt import-commit" had generated
> invalid patch names.

Thanks, I ran into this just last night (although I had manually
created the patch file from an e-mail I received instead of using
"guilt import-commit").

>  - 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?

    	       	     	    	     	       - Ted