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

Re: [StGIT PATCH] Implement a new patch identification scheme and id command

From
Karl Hasselström <kha@treskal.com>
Date
Jun 16, 2008, 14:08 UTC
Message-ID
<20080616140857.GA24433@diana.vm.bytemark.co.uk>
In-Reply-To
<b0943d9e0806160630m12f5bc7x39053e6c81d983c0@mail.gmail.com>
On 2008-06-16 14:30:32 +0100, Catalin Marinas wrote:
Show 8 quoted lines
> What about supporting patch ranges with the new id format, something
> like:
>
>   branch:patch1..patch2,patch3
>
> or
>
>   branch:patch1..patch2 branch:patch3

Yes, that's a good idea; the endpoints of a range have to be on the same branch no matter what, so having the branch: prefix apply to both of the endpoint patches in "branch:patch1..patch2" is a good idea.

I'm not sure if the comma notation is worth it. And if it turns out to have been useful, we can just advise users to write

  $ stg foo branch:{p1..p2,p3}
which the shell will expand to
  $ stg foo branch:p1..p2 branch:p3
> This way we could get rid of many --branch options.
Indeed.
-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Catalin Marinas
Message 6 of 6 in “Implement a new patch identification scheme and id command”
  1. Implement a new patch identification scheme and id commandCatalin Marinas, Jun 14, 2008
  2. Catalin MarinasJun 14, 2008
  3. Karl HasselströmJun 14, 2008
  4. Catalin MarinasJun 16, 2008
  5. Catalin MarinasJun 16, 2008
  6. Karl HasselströmJun 16, 2008

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.