J. Bruce Fields wrote: > On Fri, Mar 23, 2007 at 03:23:55PM +0100, Jakub Narebski wrote: >> J. Bruce Fields wrote: >>> >>> The input to git-am is email, not log messages. >> >> But that means that commit message which doesn't have empty line after >> first line cannot be send via git-send-email + git-am without changes, >> not be subject to git-rebase (which uses git-am machinery unless invoked >> with --merge option) without changing commit message, isn't it? > > Yup. > > Doesn't seem like a big deal to me. But then it'd also seem more > sensible to me if git-rebase worked directly with the original commits > rather than going through git-format-patch/git-am. Maybe what I want is > a git-cherry-pick that will accept a range. git-rebase works directly with original commits if you use merge driven git-rebase, with --merge option (or -s <strategy> option, which implies --merge), which is present since Jun 21, 2006. BTW. I do wonder if "git rebase --merge" accepts and honors -C<n> option... -- 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