On Tue, 8 July 2008, Stephan Beyer wrote: > Junio C Hamano <gitster@xxxxxxxxx> wrote: >> >> I _really_ wanted to merge the basic bits and rewrite of "am" at least to >> pu tonight, but I had to drop them after noticing that it does not seem to >> handle --rebasing at all (it parses to set $rebasing but after that where >> does that bit go? > > Yes, you are right that am --rebasing is a no-op. > That option was a little mystery to me, because it seemed to do nothing > special, but I'll check again (bash-completion etc) and do appropriate > changes. Undocumented option '--rebasing' to git-am is internal option changing git-am behavior to be better used by git-rebase, namely it does not change commit message even if it doesn't follow git commit message convention, for example if it begins not with single line summary of commit, separated by empty line, but by multi-line paragraph. See also t/t3405-rebase-malformed.sh Although I am not sure if when rebase is rewritten using git-sequencer implementing "git am --rebasing" would be truly needed. On the other hand side it would be nice to have some _documented_ option which would allow to git-am mail messages with commits not following git commit messages convention... -- Jakub Narebski Poland -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
