From: John Keeping <john@keeping.me.uk>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug with rev-list --reverse?
Date: Thu, 18 Apr 2013 11:26:44 +0100 [thread overview]
Message-ID: <20130418102644.GY2278@serenity.lan> (raw)
In-Reply-To: <CAMP44s25mUA1M+K+YKaC=bz3Dr7kSDyXK5g2ot8i+1EPy8zRhA@mail.gmail.com>
On Thu, Apr 18, 2013 at 05:17:14AM -0500, Felipe Contreras wrote:
> If I do these:
>
> % git log --oneline -1 v1.8.1.5^..v1.8.1.6
> % git log --oneline --reverse -1 v1.8.1.5^..v1.8.1.6
>
> I expect to get a different output, and not both showing v1.8.1.6.
> Wouldn't you agree?
I expect to get the same output. This is probably because I consider
--reverse to be an output filter. So I expect to show the commits
"v1.8.1.5^..v1.8.1.6 -1" which selects a single commit and then show
that in reverse order.
next prev parent reply other threads:[~2013-04-18 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 10:17 Bug with rev-list --reverse? Felipe Contreras
2013-04-18 10:26 ` John Keeping [this message]
2013-04-18 11:15 ` Felipe Contreras
2013-04-18 10:47 ` Peter Krefting
2013-04-18 11:18 ` Felipe Contreras
2013-04-18 14:25 ` Thomas Rast
2013-04-18 17:25 ` 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=20130418102644.GY2278@serenity.lan \
--to=john@keeping.me.uk \
--cc=felipe.contreras@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.
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).