From: Neil Horman <nhorman@tuxdriver.com>
Date: Mon, 26 Mar 2012 17:20:28 GMT
Subject: Re: odd behavior with git-rebase
Message-ID: <20120326172028.GB12843@hmsreliant.think-freely.org>
In-Reply-To: <7v1uofqoa7.fsf@alter.siamese.dyndns.org>

On Mon, Mar 26, 2012 at 10:12:48AM -0700, Junio C Hamano wrote:
> Neil Horman <nhorman@tuxdriver.com> writes:
> 
> > Is there a way to differentiate a commit that is made empty as the result of a
> > previous patch in the rebase, and a commit that is simply empty?
> 
> An empty commit has the same tree object as its parent commit.
> 
Got it, thanks!

> > I agree, I think perhaps adding an --allow-empty option to the rebase logic, so
> > that empty commits (or perhaps just initially empty, as opposed to commits made
> > empty) would be very beneficial.
> 
> Yeah, that probably may make sense.
> 
Ok, cool, I'll have a patch in a few days, thanks!
Neil