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

Re: Extending "extended SHA1" syntax to traverse through gitlinks?

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 23, 2016, 16:39 UTC
Message-ID
<xmqqy43nwibj.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<ab6e29c1-ea6d-c1c5-e69f-867c16cc736a@gmail.com>
Jakub Narębski <jnareb@gmail.com> writes:
Show 8 quoted lines
> Especially that for submodules you need:
>
> $ git --git-dir=subdir/.git cat-file -p $(git rev-parse HEAD:subdir):file
>
> (or something like that), assuming that you start in supermodule.
>   ...
>
> But perhaps '//' would be better.

If the users have to know where they need to use different separator, I do not think it is worth complicating the plumbing to do this for them. I'd rather keep things simple, and let the users build complex stuff on top of the plumbing.

Previous: Josh Triplett
Message 13 of 13 in “Extending "extended SHA1" syntax to traverse through gitlinks?”
  1. Josh TriplettAug 20, 2016
  2. Jakub NarębskiAug 21, 2016
  3. Josh TriplettAug 21, 2016
  4. Jakub NarębskiAug 22, 2016
  5. Josh TriplettAug 23, 2016
  6. Jakub NarębskiAug 23, 2016
  7. Junio C HamanoAug 24, 2016
  8. Jakub NarębskiAug 24, 2016
  9. Josh TriplettAug 24, 2016
  10. Stefan BellerAug 24, 2016
  11. Jakub NarębskiAug 24, 2016
  12. Josh TriplettAug 24, 2016
  13. Junio C HamanoAug 23, 2016

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.