Git development
 help / color / mirror / Atom feed
From: Mark Blakeney <markb@berlios.de>
To: git@vger.kernel.org
Subject: Re: git rebase stops on empty commits
Date: Wed, 22 Jul 2009 23:01:32 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090722T224408-68@post.gmane.org> (raw)
In-Reply-To: 20090723070812.6117@nanako3.lavabit.com

Because these particular original commits were real commits ported from our
previous archaic system which for technical reasons have lost the actual file
changes (although they are trivial for each of these particular cases). But all
our commit comments are very verbose and valuable, specifically in these cases,
so it would be a shame to lose them from the linear change history.

Anyway, the question of why anybody would want empty commits is beside the main
point. The fact is that git provides this option so my bug sugestion here is
that git rebase does not cater for this existing git commit option very well. My
contention is that "git commit" supports --allow-empty so "git rebase" should as
well.

      reply	other threads:[~2009-07-22 23:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22  7:22 git rebase stops on empty commits Mark Blakeney
2009-07-22  7:44 ` Mark Blakeney
2009-07-22  8:08   ` Peter Krefting
2009-07-22 12:29     ` Mark Blakeney
2009-07-22 22:08       ` Nanako Shiraishi
2009-07-22 23:01         ` Mark Blakeney [this message]

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=loom.20090722T224408-68@post.gmane.org \
    --to=markb@berlios.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox