Re: odd behavior with git-rebase
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.
Junio C Hamano <gitster@pobox.com>