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

Re: Do we have a convenient way to refer to a specific commit in an already filtered rev-list?

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 3, 2011, 19:40 UTC
Message-ID
<7v1uutg8xw.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAEvN+1gODnGy2v2=d6NXJ8b1nBJgpqj+BkDm2eQC1xqyTKXhEg@mail.gmail.com>
Tzu-Jung Lee <roylee17@gmail.com> writes:
Show 11 quoted lines
> And also teach the rev-list to parse or interpret the 'saved' refs differently.
> So we can have the following use case:
>
>    git log branch_foo --author=some_one -S some_string --saved=cached_ref
>    git log cached_ref
>    git cherry-pick cached_ref~4
>    git format-patch cached_ref~6..cached_ref~2
>
> I often have such use cases. not sure others would be benefited from
> such feature.
> Just asking for comment. :)
It feels too much hackery for too little gain.
$ git log --oneline master..branch --author=A.U.Thor -Spickaxe >foos.txt

and working from the text file foos.txt at least would not contaminate any ref namespace and you do not have to clean them after you are done.

Previous: Tzu-Jung LeeNext: Jeff King
Message 4 of 5 in “Do we have a convenient way to refer to a specific commit in an already filtered rev-list?”
  1. Tzu-Jung LeeSep 24, 2011
  2. Jeff KingSep 27, 2011
  3. Tzu-Jung LeeOct 3, 2011
  4. Junio C HamanoOct 3, 2011
  5. Jeff KingOct 4, 2011

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.