git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Fw: sort of a bug report - git rebase dropping empty commits

From
HLHin-Tak Leung <hintak.leung@gmail.com>
Date
Jun 9, 2015, 23:16 UTC
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:
Show 15 quoted lines
> 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
Previous: Mikael Magnusson
Message 3 of 3 in “Fwd: Fw: sort of a bug report - git rebase dropping empty commits”
  1. Hin-Tak LeungMay 7, 2015
  2. Mikael MagnussonMay 7, 2015
  3. Hin-Tak LeungJun 9, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.