From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 26 Mar 2012 17:12:48 GMT
Subject: Re: odd behavior with git-rebase
Message-ID: <7v1uofqoa7.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20120324165536.GA17932@neilslaptop.think-freely.org>

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.

> 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.