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 <mika...@gmail.com> wrote: > On Thu, May 7, 2015 at 2:19 AM, Hin-Tak Leung <hintak.le...@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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
