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

Re: stgit restrictions on patch names

From
Karl Hasselström <kha@treskal.com>
Date
Oct 26, 2007, 07:29 UTC
Message-ID
<20071026072924.GA11286@diana.vm.bytemark.co.uk>
In-Reply-To
<20071025194808.GV26436@nan92-1-81-57-214-146.fbx.proxad.net>
On 2007-10-25 21:48:08 +0200, Yann Dirson wrote:
Show 5 quoted lines
> Do we want to:
>
> - implement a mechanism for checking beforehand that the operation
> will not fail? Seems awkward to duplicate checks already found
> elsewhere.

Duplication is bad. Calling the same verification function more times than necessary is still bad, but maybe not so bad that it wouldn't be OK.

> - wait for proper transactions so we can rollback on error ?

Yes, this is what we should aim for. I'm working on code that'll eventually give us this if it pans out.

> - on clone error, delete the newly-created stack ? I'd vote for this
> one, until the previous one gets done.
Seems reasonable.
> => is there any particular reason why we would refuse "+" ?
Not that I can think of at the moment, except maybe future-proofing.
-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Yann DirsonNext: Catalin Marinas
Message 2 of 3 in “stgit restrictions on patch names”
  1. Yann DirsonOct 25, 2007
  2. Karl HasselströmOct 26, 2007
  3. Catalin MarinasOct 29, 2007

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.