From: "Marco Costalba" <mcostalba@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] revision limiter in git-rev-list
Date: Tue, 6 Jun 2006 13:46:23 +0200 [thread overview]
Message-ID: <e5bfff550606060446rc9160cbt948ceededeb22766@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2006-06-06 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 8:36 [RFC] revision limiter in git-rev-list Marco Costalba
2006-06-06 10:29 ` Junio C Hamano
2006-06-06 11:14 ` Marco Costalba
2006-06-06 11:46 ` Marco Costalba [this message]
2006-06-06 18:29 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5bfff550606060446rc9160cbt948ceededeb22766@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).