Re: bugreport: stgit cannot export empty patch

From: Junio C Hamano <gitster@pobox.com>
Date: May 18, 2012, 21:20 UTC
Message-ID: <xmqqboll2nl0.fsf@junio.mtv.corp.google.com>
In-Reply-To: <CAPk5vtzpUHgL_dfJLJHgKsaNPZodx1jbTRQpRdoj01RRPRoBfg@mail.gmail.com>

Stepan Koltsov <stepan.koltsov@jetbrains.com> writes:

Show 15 quoted lines

> stgit fails to export empty patches:
>
> % stg new empty-patch -m 'asasas'
> Now at patch "empty-patch"
> % stg export empty-patch
> Checking for changes in the working directory ... done
> fatal: unrecognized input
> stg export: git failed with code 128
> zsh: exit 2     stg export empty-patch
>
> % stg --version
> Stacked GIT 0.16-3-g67cf
> git version 1.7.9.1
> Python version 2.7.1 (r271:86832, Jul 31 2011, 19:30:53)
> [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)]

I don't use (or read the sources to) StGIT, but isn't the whole point of "stg export" to "convert your StGIT patches into patch files"? For an empty commit, what is an appropriate output? IOW, is it reasonable to have an empty commit in your history if you are planning to "stg export" it?