{"thread":{"id":"30560","subject":"bugreport: stgit cannot export empty patch","startedAt":"2012-05-18T20:57:56Z","lastAt":"2013-01-10T23:16:57Z","messageCount":4,"participants":["Stepan Koltsov","Junio C Hamano","bryanlarsen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"191678","messageId":"CAPk5vtzpUHgL_dfJLJHgKsaNPZodx1jbTRQpRdoj01RRPRoBfg@mail.gmail.com","threadId":"30560","inReplyTo":null,"subject":"bugreport: stgit cannot export empty patch","fromName":"Stepan Koltsov","fromEmail":"stepan.koltsov@jetbrains.com","sentAt":"2012-05-18T20:57:56Z","receivedAt":"2012-05-18T20:57:56Z","isPatch":false,"sender":{"key":"stepan.koltsov@jetbrains.com","avatar":null},"body":"Hi.\n\nstgit fails to export empty patches:\n\n% stg new empty-patch -m 'asasas'\nNow at patch \"empty-patch\"\n% stg export empty-patch\nChecking for changes in the working directory ... done\nfatal: unrecognized input\nstg export: git failed with code 128\nzsh: exit 2     stg export empty-patch\n\n% stg --version\nStacked GIT 0.16-3-g67cf\ngit version 1.7.9.1\nPython version 2.7.1 (r271:86832, Jul 31 2011, 19:30:53)\n[GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)]\n\n-- \nStepan Koltsov\n"},{"id":"191681","messageId":"xmqqboll2nl0.fsf@junio.mtv.corp.google.com","threadId":"30560","inReplyTo":"CAPk5vtzpUHgL_dfJLJHgKsaNPZodx1jbTRQpRdoj01RRPRoBfg@mail.gmail.com","subject":"Re: bugreport: stgit cannot export empty patch","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-05-18T21:20:27Z","receivedAt":"2012-05-18T21:20:27Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Stepan Koltsov <stepan.koltsov@jetbrains.com> writes:\n\n> stgit fails to export empty patches:\n>\n> % stg new empty-patch -m 'asasas'\n> Now at patch \"empty-patch\"\n> % stg export empty-patch\n> Checking for changes in the working directory ... done\n> fatal: unrecognized input\n> stg export: git failed with code 128\n> zsh: exit 2     stg export empty-patch\n>\n> % stg --version\n> Stacked GIT 0.16-3-g67cf\n> git version 1.7.9.1\n> Python version 2.7.1 (r271:86832, Jul 31 2011, 19:30:53)\n> [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)]\n\nI don't use (or read the sources to) StGIT, but isn't the whole point of\n\"stg export\" to \"convert your StGIT patches into patch files\"?  For an\nempty commit, what is an appropriate output?  IOW, is it reasonable to\nhave an empty commit in your history if you are planning to \"stg export\"\nit?\n"},{"id":"191685","messageId":"CAPk5vtyc1gHB=31CPDpk=s4QE+Wtp-8wMJDuV1F=R11MfERdTw@mail.gmail.com","threadId":"30560","inReplyTo":"xmqqboll2nl0.fsf@junio.mtv.corp.google.com","subject":"Re: bugreport: stgit cannot export empty patch","fromName":"Stepan Koltsov","fromEmail":"stepan.koltsov@jetbrains.com","sentAt":"2012-05-18T22:26:08Z","receivedAt":"2012-05-18T22:26:08Z","isPatch":false,"sender":{"key":"stepan.koltsov@jetbrains.com","avatar":null},"body":"On Sat, May 19, 2012 at 1:20 AM, Junio C Hamano <gitster@pobox.com> wrote:\n> Stepan Koltsov <stepan.koltsov@jetbrains.com> writes:\n>\n>> stgit fails to export empty patches:\n>>\n>> % stg new empty-patch -m 'asasas'\n>> Now at patch \"empty-patch\"\n>> % stg export empty-patch\n>> Checking for changes in the working directory ... done\n>> fatal: unrecognized input\n>> stg export: git failed with code 128\n>> zsh: exit 2     stg export empty-patch\n>>\n>> % stg --version\n>> Stacked GIT 0.16-3-g67cf\n>> git version 1.7.9.1\n>> Python version 2.7.1 (r271:86832, Jul 31 2011, 19:30:53)\n>> [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)]\n>\n> I don't use (or read the sources to) StGIT, but isn't the whole point of\n> \"stg export\" to \"convert your StGIT patches into patch files\"?  For an\n> empty commit, what is an appropriate output?  IOW, is it reasonable to\n> have an empty commit in your history if you are planning to \"stg export\"\n> it?\n\nI'm executing stg export to back up. If series contains empty patches,\nbackup fails.\n\nScenario: I started some work, created new empty patch, but did\nnothing, decided to go home, and do backup of the whole series before\nleaving. Backup fails.\n\nAFAIU there's no simpler way to backup stg series than executing\n\n% stg export `stg series --noprefix`\n\n-- \nStepa\n"},{"id":"206477","messageId":"1357859817532-7574691.post@n2.nabble.com","threadId":"30560","inReplyTo":"xmqqboll2nl0.fsf@junio.mtv.corp.google.com","subject":"Re: bugreport: stgit cannot export empty patch","fromName":"bryanlarsen","fromEmail":"bryan@larsen.st","sentAt":"2013-01-10T23:16:57Z","receivedAt":"2013-01-10T23:16:57Z","isPatch":false,"sender":{"key":"bryan@larsen.st","avatar":"https://avatars.githubusercontent.com/u/32073?v=4"},"body":"Junio C Hamano writes:\n\n> Stepan Koltsov &lt;stepan.koltsov@&gt; writes:\n>> stgit fails to export empty patches:\n>>\n>> % stg new empty-patch -m 'asasas'\n>> Now at patch \"empty-patch\"\n>> % stg export empty-patch\n>> Checking for changes in the working directory ... done\n>> fatal: unrecognized input\n>> stg export: git failed with code 128\n>> zsh: exit 2     stg export empty-patch\n>>\n>> % stg --version\n>> Stacked GIT 0.16-3-g67cf\n>> git version 1.7.9.1\n>> Python version 2.7.1 (r271:86832, Jul 31 2011, 19:30:53)\n>> [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)]\n\n> I don't use (or read the sources to) StGIT, but isn't the whole point of\n> \"stg export\" to \"convert your StGIT patches into patch files\"?  For an\n> empty commit, what is an appropriate output?  IOW, is it reasonable to\n> have an empty commit in your history if you are planning to \"stg export\"\n> it?\n\nHere's another example where the functionality is useful: \nhttps://github.com/Hobo/agility-gitorial-patches is used to build\nhttp://cookbook.hobocentral.net/tutorials/agility\n\nEach commit/patch becomes a step in the tutorial.  Some tutorial steps don't\nhave any code attached to them.\n\nIn the past, an export of an empty commit would yield a patch where the last\nthree lines were\n\n> ---\n>  0 files changed, 0 insertions(+), 0 deletions(-)\n>\n\nThe latest version of stgit along with git v1.6 eliminates the error.  A\nbisection identifies cc64b318f26c9e176c4f07b1a459a86e7a04c4eb as the source\nof the problem.\n\nThanks,\nBryan\n\n\n\n\n--\nView this message in context: http://git.661346.n2.nabble.com/bugreport-stgit-cannot-export-empty-patch-tp7559494p7574691.html\nSent from the git mailing list archive at Nabble.com.\n"}]}