From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: "Shawn Pearce" <spearce@spearce.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: --max-count useless with git-rev-list's --reverse
Date: Tue, 08 Mar 2011 09:34:52 +0100 [thread overview]
Message-ID: <4D75EA2C.9010200@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTin19c8jP9D2iQbP8XVLo4O_4+Wf+exwB-inCBQV@mail.gmail.com>
Jay Soffian venit, vidit, dixit 08.03.2011 08:35:
> On Mon, Mar 7, 2011 at 2:40 PM, Shawn Pearce <spearce@spearce.org> wrote:
>> On Mon, Mar 7, 2011 at 11:17, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>>> From the manpage:
>>
>> No. Its applied after, otherwise things like "git log -n 5 --reverse"
>
> I think I was surprised the first time I tried to combine those
> options as well, but in retrospect the reason is obvious. Nonetheless,
> I think this has come up on the list a few time, so... Ævar, would you
> mind submitting a documentation patch?
Due to gmane lag, I replied to AAB's post only, but I bet you'll find
the patches.
Cheers,
Michael
next prev parent reply other threads:[~2011-03-08 8:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 19:17 --max-count useless with git-rev-list's --reverse Ævar Arnfjörð Bjarmason
2011-03-07 19:40 ` Shawn Pearce
2011-03-08 7:35 ` Jay Soffian
2011-03-08 8:34 ` Michael J Gruber [this message]
2011-03-08 8:30 ` Michael J Gruber
2011-03-08 8:31 ` [PATCH 1/3] rev-list-options.txt: typo fix Michael J Gruber
2011-03-08 8:31 ` [PATCH 2/3] git-log.txt,rev-list-options.txt: -n/--max-count is commit limiting Michael J Gruber
2011-03-08 19:59 ` Junio C Hamano
2011-03-09 7:11 ` Michael J Gruber
2011-03-08 8:31 ` [PATCH 3/3] git-log.txt,rev-list-options.txt: put option blocks in proper order Michael J Gruber
2011-03-09 23:38 ` Junio C Hamano
2011-03-10 7:50 ` Michael J Gruber
2011-03-08 19:56 ` [PATCH 1/3] rev-list-options.txt: typo fix Junio C Hamano
2011-03-09 7:07 ` Michael J Gruber
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=4D75EA2C.9010200@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=spearce@spearce.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 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.