On Thu, 16 Jun 2016 05:59:47 -0400 Jeff King <peff@xxxxxxxx> wrote: > On Mon, Jun 13, 2016 at 08:28:18AM +0200, Stefan Tauner wrote: > > > I am trying to do a major cleanup of the repository in one of my > > projects (and switch from git-svn to native git). I have developed a > > commit-filter script over the last months that massages partially > > dreadful commit messages into something acceptable. While I am not 100% > > sure I think that upgrading git has broken it partially. AFAICT since > > the update the commit-filter does not get the original message anymore > > but at least the subject/first paragraph is run through a pager or > > something similar: > > The first line is broken into multiple lines (i.e. some line breaks are > > inserted about every 72 characters where none have been before). > > There are some output formats that will wrap lines, but by default, > filter-branch should not be using them (and I could not reproduce the > issue in a simple test). Can you show us what your commit-filter looks > like? Thanks for your answer. I have tried to reproduce it in other (newly created) repositories but failed. However, it seems to relate to some kind of persistent paging setting, is that possible? git config -l does not show anything suspicious. The following commands produce paged output: git show hash git show --pretty=%B git log hash^..hash Commit message in gitk These do NOT produce paged output: git patch hash^..hash Commit message in gitg 0.2.7 This is the script I tried to use to reproduce the problem: #!/bin/bash export LC_ALL=C input=$(cat) echo "=========================== $input ===========================" >> /tmp/paging_bug.txt git commit-tree "$@" -m "$input" -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner -- 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