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

[RFC] subtree: use say and exit 0 rather than die in case of no new revision found scenario

From
Claus Schneider <claus.schneider@eficode.com>
Date
May 6, 2020, 13:11 UTC
Message-ID
<CA+GP4brpeGhBy3LF0LomDO-AOEZS02tOi2phQ4e1XoTGgeAx2w@mail.gmail.com>
In-Reply-To
<CA+GP4boXi4tW23Z6CDF2v_ch2_7_dqhB_POAhi1FfYrEBG4DWQ@mail.gmail.com>
Hi..

Currently subtree dies if "No new revisions found" which is hard as it is a non-operation.

I suggest using the "say" command rather than "die".

It will then become easier just to call "git subtree split" and you do not need to handle this special case.

Patches can be found here: https://github.com/git/git/commit/fe435a1ba128698f6acb69ee1891c45be32610fa

Best regards Claus Schneider

Next: Taylor Blau
Message 1 of 2 in “[RFC] subtree: use say and exit 0 rather than die in case of no new revision found scenario”
  1. Claus SchneiderMay 6, 2020
  2. Taylor BlauMay 6, 2020

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.