From: Hin-Tak Leung <hintak.leung@gmail.com>
Date: Tue, 09 Jun 2015 23:16:04 GMT
Subject: Re: Fw: sort of a bug report - git rebase dropping empty commits
Message-ID: <CAJMB+NgqcydSzt--L+2kLmtNYp2kzhifEdYfgnEbcbwOovH_7A@mail.gmail.com>
In-Reply-To: <CAHYJk3QOuo=p26OAnkKmrPS0SzpdJGvB=Fm=jiMMDDJo13zi9A@mail.gmail.com>

Argh, thanks a lot!  Should have read the man page better. OTOH,
I expect 'git commit --allow-empty' being needed, but 'git rebase --keep-empty'
comes somewhat as a surprise - I wasn't expecting git rebase to commit
each in turn,
but of course that's what it does.

On 7 May 2015 at 01:47, Mikael Magnusson <mikachu@gmail.com> wrote:
> On Thu, May 7, 2015 at 2:19 AM, Hin-Tak Leung <hintak.leung@gmail.com> wrote:
>> Repost from another account. vger.kernel.org seems not
>> to like postings from my other alias (which goes through
>> yahoo).
>>
>>> (please cc - I am not a subscriber)
>>>
>>> Recently I have started to keep some notes in git repo's
>>> with --allow-empty - i.e. the meaningful content is
>>> the commit message and the date itself, not the diff.
>
> Use the git rebase --keep-empty option?
>
> --
> Mikael Magnusson