Re: Un-paged commit messages in git filter-branch's commit-filter?
- From
- Stefan Tauner <stefan.tauner@gmx.at>
- Date
- Aug 6, 2016, 09:40 UTC
- Message-ID
- <0M0gcI-1bFxtH2ZLy-00usFU@mail.gmx.com>
- In-Reply-To
- <20160801232429.mb43wxev5lyhxyiw@sigill.intra.peff.net>
On Mon, 1 Aug 2016 19:24:29 -0400 Jeff King <peff@peff.net> wrote:
> So could it be that your lines actually _are_ broken in the git objects, > but "%s" and other tools try to salvage them as a single subject?
YES! :) Thanks so much! I was apparently ignoring this trivial explanation because I was too much persuaded that the actual commits had missing line breaks and only something in git was adding them. But it is actually the other way around as you said: the few commands that print the overlong lines are those that rely on %s. gitg for example parses the output of the following: git show --num-stat --pretty="format:%s%n%n%b%n\x01" I was not aware that %s lumps lines together if it does not find a proper subject on the first line.
I can work with that now. Thanks again!
-- Kind regards/Mit freundlichen Grüßen, Stefan Tauner