From: Stefan Tauner <stefan.tauner@gmx.at>
To: git@vger.kernel.org
Subject: Un-paged commit messages in git filter-branch's commit-filter?
Date: Mon, 13 Jun 2016 08:28:18 +0200 [thread overview]
Message-ID: <0McmFl-1aux6M2oV7-00Hv9A@mail.gmx.com> (raw)
Hello,
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).
I have tried to run "git --no-pager filter-branch ..." to no avail. I
have briefly looked at the source but could not find any proofs...
Any hints would be appreciated. This is how I run my script:
tmpvar="$(</home/.....sh)" ; git --no-pager filter-branch -f --commit-filter "$tmpvar" --tag-name-filter cat -- HEAD
--
Kind regards, Stefan Tauner
next reply other threads:[~2016-06-13 6:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 6:28 Stefan Tauner [this message]
2016-06-16 9:59 ` Un-paged commit messages in git filter-branch's commit-filter? Jeff King
2016-07-31 16:39 ` Stefan Tauner
2016-08-01 21:36 ` Jeff King
2016-08-01 21:49 ` Stefan Tauner
2016-08-01 23:24 ` Jeff King
2016-08-02 0:07 ` Eric Wong
2016-08-06 9:40 ` Stefan Tauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0McmFl-1aux6M2oV7-00Hv9A@mail.gmx.com \
--to=stefan.tauner@gmx.at \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).