git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-p4: Handle p4 submit failure

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 30, 2015, 20:23 UTC
Message-ID
<xmqqziz0jeb5.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<5633CABA.1000003@diamand.org>
Luke Diamand <luke@diamand.org> writes:
Show 26 quoted lines
> On 30/10/15 17:57, Junio C Hamano wrote:
>> Etienne Girard <etienne.g.girard@gmail.com> writes:
>>
>>> Yes, however if `p4 submit` fails the corresponding "Command failed"
>>> error message is displayed, and the p4 error message itself is
>>> displayed if any.
>>> Tthe script will also terminate successfully if self.edit_template
>>> returns false but it will exit with error code 1 if p4 submit fails.
>>>
>>> So the user will get "Command failed: [...]" followed by "Submission
>>> cancelled, undoing p4 changes", to let him know that the script failed
>>> because of p4 and that nothing was submitted.
>>
>> OK, then it sounds like all I have to do is to update the log
>> message with the "How about this" version and correct the authorship
>> to use your murex address, and then wait for reviews from real "git
>> p4" reviewers.
>>
>
> Looks good to me. Nice use of try...finally.
>
> One very small thing - test t9807-git-p4-submit.sh is now failing with
> this change.
>
> That's because it tries to delete one of the files it created, but you
> are now deleting it already! Could you just update that please?

I'll ask Etienne include that change in a reroll, as my environment is not equipped to run any p4 tests.

Thanks.
Previous: Luke Diamand
Message 6 of 6 in “git-p4: Handle p4 submit failure”
  1. git-p4: Handle p4 submit failureEtienne Girard, Oct 28, 2015
  2. Junio C HamanoOct 30, 2015
  3. Etienne GirardOct 30, 2015
  4. Junio C HamanoOct 30, 2015
  5. Luke DiamandOct 30, 2015
  6. Junio C HamanoOct 30, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.