Re: Log messages beginning # and git rebase -i
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Jul 28, 2015, 00:53 UTC
- Message-ID
- <CACsJy8BE8GOj6g-pH7UgQ6sEQk_ZbtgqHkAHQvTkCDJU=2dBYw@mail.gmail.com>
- In-Reply-To
- <CAPig+cRT6=YCHz+phfE+84y27ey-6ScjPxP2cHiVqumJmR6mOw@mail.gmail.com>
On Tue, Jul 28, 2015 at 6:25 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
Show 12 quoted lines
> On Mon, Jul 27, 2015 at 7:38 AM, Ed Avis <eda@waniasset.com> wrote: >> git commit will happily let you specify log messages beginning with #. >> But then on git rebase -i, when squashing some commits, the editing for the >> combined log message treats lines beginning with # as comments. This means >> that if you are not careful the commit message can get lost on rebasing. >> >> I suggest that git rebase should add an extra space at the start of existing >> log message lines which begin with #. That is a bit of a kludge but it is >> better than losing them because they got mixed up with comments. > > 'git rebase --interactive' respects the core.commentChar configuration > variable, which you can set to some value other than '#'.
Yeah. I recommend setting it to 'auto' so it will pick an unused character as separator (most of the time, don't push it too hard)
-- Duy