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

[StGIT RFC] Changing patch@branch syntax

From
Yann Dirson <ydirson@altern.org>
Date
May 15, 2007, 22:03 UTC
Message-ID
<20070515220310.GJ16903@nan92-1-81-57-214-146.fbx.proxad.net>

The patch@branch syntax is annoying, at least for bash-completion purposes: we don't want to provide all possible completions accross all branches, yet we'd like to get completion for foreign patches.

Another place where I feel it is bad is when using the full "patch@branch//top" syntax: the MSB is in the middle, and the LSB is on the right.

Both issues would be solved by switching to a MSB ordering, with a way to distinguish branchnames when given. Something similar to pathnames would fit well - eg. [/branchname/]patchname[//top]. However, I'm not sure using slashes would be a good choice, precisely because of the similarity with real pathnames. But we don't have so many separator chars that are not special in one way or another, and would require quoting them to avoid more user confusion.

What do you think ?
-- 
Yann.
Next: Karl Hasselström
Message 1 of 12 in “[StGIT RFC] Changing patch@branch syntax”
  1. Yann DirsonMay 15, 2007
  2. Karl HasselströmMay 16, 2007
  3. Catalin MarinasMay 22, 2007
  4. Yann DirsonMay 22, 2007
  5. Yann DirsonJun 21, 2007
  6. Catalin MarinasJun 22, 2007
  7. Yann DirsonJun 22, 2007
  8. Catalin MarinasJun 22, 2007
  9. Yann DirsonJun 24, 2007
  10. Catalin MarinasJun 25, 2007
  11. Yann DirsonJun 26, 2007
  12. Yann DirsonJul 6, 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.