From: Miklos Vajna <vmiklos@frugalware.org>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: git@vger.kernel.org
Subject: Re: Why does "git log --reverse -1" print the HEAD commit?
Date: Sat, 31 May 2008 16:24:08 +0200 [thread overview]
Message-ID: <20080531142408.GL29404@genesis.frugalware.org> (raw)
In-Reply-To: <20080531141102.GA3035@mithlond.arda.local>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On Sat, May 31, 2008 at 05:11:02PM +0300, Teemu Likonen <tlikonen@iki.fi> wrote:
> It feels wrong that "git log -1" and "git log --reverse -1" both print
> the same commit: HEAD. Why is that?
>
> Since "git log --reverse" starts from the bottom I'd have expected "-1"
> to print one commit from the bottom.
-1 limits the commit list to one element and then it prints that range
in reverse order, which is the same for a single commit.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-05-31 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 14:11 Why does "git log --reverse -1" print the HEAD commit? Teemu Likonen
2008-05-31 14:24 ` Miklos Vajna [this message]
2008-05-31 14:33 ` Teemu Likonen
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=20080531142408.GL29404@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=tlikonen@iki.fi \
/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).