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

Re: [RFC] revision limiter in git-rev-list

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Jun 6, 2006, 11:46 UTC
Message-ID
<e5bfff550606060446rc9160cbt948ceededeb22766@mail.gmail.com>
In-Reply-To
<7v7j3uvapa.fsf@assigned-by-dhcp.cox.net>
>
> While I really do not think this belongs to rev-list, I suspect
> what you want is a command that takes a set of commits you are
> interested in and gives you an abbreviated topology across them.
I was thinking at an extension of git-rev-list because
1) Current git-rev-list options are quite orthogonal with rev limiter.
As example in previous given examples -n and --parents options are
used and I think more could be used with
interesting results.

Current git-rev-list options are a lot and are very powerful, it's a pity if this new feature do not inherit them.

2) This feature could be seen as a generalization of path limiting.
>From today:
  git-rev-list  HEAD -- <path 1>  <path 2>  ...   <path n>

To possible: git-rev-list HEAD -- <obj 1> <obj 2> ... <obj n>

Where obj == <path> || obj == <commit sha> || obj == <something else I didn't think of>

Of course we need a (syntactic) way to disambiguate the arguments after '--' but the results are very powerful and general, as example we could mix commit objects _and_ paths in git-rev-list command line (git-rev-list HEAD -- foo.c tag1) and also be able to use the full set of git-rev-list options before the '--'

     Marco
Previous: Marco CostalbaNext: Junio C Hamano
Message 4 of 5 in “[RFC] revision limiter in git-rev-list”
  1. Marco CostalbaJun 6, 2006
  2. Junio C HamanoJun 6, 2006
  3. Marco CostalbaJun 6, 2006
  4. Marco CostalbaJun 6, 2006
  5. Junio C HamanoJun 6, 2006

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.