All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: git@vger.kernel.org
Subject: Re: Reachability lists in git
Date: Tue, 18 Nov 2014 11:41:29 -0800	[thread overview]
Message-ID: <20141118194129.GI6527@google.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1411181354320.4374-100000@iolanthe.rowland.org>

Hi,

Alan Stern wrote:

> The "git rev-list A ^B" command lists all the commits that are
> reachable from A but not from B.  Is there a comparable command for the
> converse relation, that is, a command to list all the commits that A is
> reachable from but B isn't?
>
> And if there is such a command, can the output be limited to just the
> latest commits?  That is, list commit X if and only if A is reachable
> from X, B isn't reachable from X, and B is reachable from each of X's
> children?

Someone else can answer your direct question, but you've got my
curiosity.  What is the application?

--ancestry-path is my current favorite tool for walking-forward needs.

Curious,
Jonathan

  reply	other threads:[~2014-11-18 19:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 19:03 Reachability lists in git Alan Stern
2014-11-18 19:41 ` Jonathan Nieder [this message]
2014-11-18 20:13   ` Junio C Hamano
2014-11-18 20:22     ` Jonathan Nieder
2014-11-18 20:27       ` Jonathan Nieder
2014-11-18 20:33       ` Junio C Hamano
2014-11-18 20:29   ` Alan Stern
2014-11-18 20:32     ` Jonathan Nieder
2014-11-18 20:45       ` Alan Stern
2014-11-18 21:05         ` Junio C Hamano
2014-11-18 21:11           ` Junio C Hamano
2014-11-18 21:16           ` Alan Stern
2014-11-18 21:22             ` Junio C Hamano
2014-11-18 21:37               ` Alan Stern

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=20141118194129.GI6527@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.