From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Francis Moreau <francis.moro@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Splitting a rev list into 2 sets
Date: Thu, 20 Jun 2013 19:17:31 +0530 [thread overview]
Message-ID: <CALkWK0k_2jzQNBjLKZ4SDc9vqoZuQ7937dnO6Z_Ye4Ha+FNcag@mail.gmail.com> (raw)
In-Reply-To: <CAC9WiBgmswSqDHS3XOubvkY6GhBqrQ3YdwgKR4npqHM-kLJuMA@mail.gmail.com>
Francis Moreau wrote:
> Basically I have an initial set (or can be several different sets)
> expressed as a revision specification described by git-rev-list man
> page. I just want to find the common set of commit which are part of
> the initial sets *and* is reachable by master.
That's just a generic list intersection between
[a, b, c] and [d, e, f]
no? [a, b, c] is a list you built up somehow, and [d, e, f] comes
from $(git rev-list master), right?
You could go about determining the revision walk boundaries and
combine them to set up a revision walk to splice the master line, but
what is the point of that? You'll only be painting yourself into a
design-corner (you won't be able to do other kinds of filtering), and
going around your head to touch your nose. You precisely want list
intersection: so write an efficient list intersection in the language
of your choice. Why is it a poor man's solution? If anything, your
convoluted rev-list solution will probably be more complicated,
slower, and bug-ridden.
next prev parent reply other threads:[~2013-06-20 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 10:14 Splitting a rev list into 2 sets Francis Moreau
2013-06-20 11:26 ` Ramkumar Ramachandra
2013-06-20 13:12 ` Francis Moreau
2013-06-20 13:47 ` Ramkumar Ramachandra [this message]
2013-06-21 7:15 ` Francis Moreau
2013-06-21 7:19 ` Ramkumar Ramachandra
2013-06-20 13:04 ` Phil Hord
2013-06-20 13:17 ` Francis Moreau
2013-06-20 13:20 ` Thomas Rast
2013-06-20 16:24 ` Francis Moreau
2013-06-24 9:59 ` Thomas Rast
2013-06-25 8:09 ` Francis Moreau
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALkWK0k_2jzQNBjLKZ4SDc9vqoZuQ7937dnO6Z_Ye4Ha+FNcag@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=francis.moro@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).