Git development
 help / color / mirror / Atom feed
From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Kevin Ballard <kevin@sb.org>, git list <git@vger.kernel.org>
Subject: Re: [BUG] git rev-list --no-walk A B C sorts by commit date incorrectly
Date: Tue, 11 Jan 2011 19:54:53 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.1.10.1101111949230.856@debian> (raw)
In-Reply-To: <7vaaja8sxd.fsf@alter.siamese.dyndns.org>

On Sat, 8 Jan 2011, Junio C Hamano wrote:

> Junio C Hamano <gitster@pobox.com> writes:
> 
> > "git rev-list --no-walk ^HEAD~3 HEAD"?  Isn't it a nonsense?  If it is "no
> > walk", then why do you even list a negative one?
> 
> The above was my thinko.
> 
> When you explicitly give range to no-walk, you override that no-walk with
> "please walk".  This is primarily to help Linus who wanted to do "git show
> HEAD~3..HEAD"---see how his thinking changed over time by comparing
> aa27e461 and f222abde.

Just a quick note: I didn't know that 'git show' was supposed to
support that syntax, so I had try it out. When I ran 'git show
origin/master..' on my branch, which was not rebase on top of
origin/master, it seemed to print the history all the way back. It
seems to stop only if all the positive refences contain the negative
reference. Is this intended? Not that it matter much, since 'git log
-p' seems to do the same thing but stops where I expect...

      reply	other threads:[~2011-01-12  0:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08  0:19 [BUG] git rev-list --no-walk A B C sorts by commit date incorrectly Kevin Ballard
2011-01-08  1:00 ` Junio C Hamano
2011-01-08  3:12   ` Kevin Ballard
2011-01-08  5:41     ` Junio C Hamano
2011-01-08  5:51       ` Kevin Ballard
2011-01-09  6:58       ` Junio C Hamano
2011-01-12  0:54         ` Martin von Zweigbergk [this message]

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=alpine.DEB.1.10.1101111949230.856@debian \
    --to=martin.von.zweigbergk@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kevin@sb.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox