On Wednesday, October 23, 2013 7:34:02 PM UTC+2, Mickey Killianey wrote:

> I expected that these two would be equivalent, and that neither would end 
> up modifying any commits:
>    git filter-branch --commit-filter '*git commit-tree $@*'
>    git filter-branch --commit-filter '*git commit-tree -F - $@*'
> However, I have discovered that the latter *does* modify some commits. 
>  Using "-F -" appears to add a terminating newline at the end of any 
> message body that doesn't already end in a newline.
> (FWIW, these commits without newlines at the end of the message appear to 
> have been introduced by merging pull-requests using the github GUI.)
> Three questions:
> Is this a bug or a feature?
> If this is a bug, where should I report it?
> If this is a feature, are there any other differences I should expect 
> between these two forms of git commit-tree?

I don't know whether this is a bug, but if you want to get in touch with 
the Git devs, here's how to find them: 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to