git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Stefan Tauner <stefan.tauner@gmx.at>
Cc: git@vger.kernel.org
Subject: Re: Un-paged commit messages in git filter-branch's commit-filter?
Date: Thu, 16 Jun 2016 05:59:47 -0400	[thread overview]
Message-ID: <20160616095947.GA15988@sigill.intra.peff.net> (raw)
In-Reply-To: <0McmFl-1aux6M2oV7-00Hv9A@mail.gmx.com>

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?

-Peff

  reply	other threads:[~2016-06-16  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  6:28 Un-paged commit messages in git filter-branch's commit-filter? Stefan Tauner
2016-06-16  9:59 ` Jeff King [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160616095947.GA15988@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=stefan.tauner@gmx.at \
    /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.
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 NNTP newsgroup(s).