git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>, git@vger.kernel.org
Subject: Re: Reachability lists in git
Date: Tue, 18 Nov 2014 12:33:24 -0800	[thread overview]
Message-ID: <xmqqmw7ouu3v.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20141118202250.GK6527@google.com> (Jonathan Nieder's message of "Tue, 18 Nov 2014 12:22:51 -0800")

Jonathan Nieder <jrnieder@gmail.com> writes:

> Junio C Hamano wrote:
>> Jonathan Nieder <jrnieder@gmail.com> writes:
>
>>> --ancestry-path is my current favorite tool for walking-forward needs.
>>
>> Curious.  I often want to answer this question:
> [...]
>> And my experiments with --ancestry-path has been less than ideal.
>
> Thanks for an example.  I've found it works okay interactively, less
> so for scripted use (so I wish there were something better, though I
> haven't sketched out what that something better would look like).
>
>>     Commit 982ac87 was reported to be faulty.  What topic was it on
>>     and at which point was it merged to 'master'?
>
>  $ git log --graph --ancestry-path 982ac87^..origin/master

Yup, that is what I've been using and was wishing that there would
be better alternatives.

  parent reply	other threads:[~2014-11-18 20:33 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
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 [this message]
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=xmqqmw7ouu3v.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --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 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).