From: Christoph Anton Mitterer <calestyo@scientia.net>
To: git@vger.kernel.org
Subject: [BUG] git mangles up commit messages on rebase
Date: Sat, 21 Feb 2015 18:48:26 +0100 [thread overview]
Message-ID: <1424540906.15539.22.camel@scientia.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Hey.
When I do a simple interactive rebase, e.g. something like this:
edit 78f3ba8 editing or just rewriting this commit
pick b621076 foo
pick e06c28e this one had a "verbatim" commit message
pick c0a447f bar
and one of the commit messages from the children I edit/rewrite had a
commit message that was edited with --cleanup=verbatim (e.g. double
newlines, etc.).
Then these get lost once I --continue and it appears that the messages
are recreated but with the default of --cleanup=default .
IMO that's quite annoying, cause when one intentionally chose e.g.
-cleanup=verbatim and made commit messages with that, then this is
probably what one wanted and it should be dumped just because of
changing another commit.
Could that possibly be solved? :)
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next reply other threads:[~2015-02-21 17:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 17:48 Christoph Anton Mitterer [this message]
2015-02-23 13:23 ` [PATCH] sequencer: preserve commit messages Michael J Gruber
2015-02-23 18:54 ` Junio C Hamano
2015-02-24 15:29 ` Michael J Gruber
2015-02-24 18:29 ` Junio C Hamano
2015-02-25 9:50 ` Michael J Gruber
2015-02-25 18:22 ` Junio C Hamano
2015-02-26 11:05 ` Michael J Gruber
2015-02-26 19:49 ` Junio C Hamano
2015-02-27 15:31 ` Michael J Gruber
2015-02-27 18:31 ` Junio C Hamano
2015-03-06 13:55 ` [PATCHv2] " Michael J Gruber
2015-03-06 18:59 ` Junio C Hamano
2015-02-25 13:44 ` [PATCH] " Christoph Anton Mitterer
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=1424540906.15539.22.camel@scientia.net \
--to=calestyo@scientia.net \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.