From: Vipul Kumar <kumar@onenetbeyond.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: List all commits of a specified file in oldest to newest order
Date: Tue, 14 Dec 2021 03:58:31 +0000 [thread overview]
Message-ID: <71d21b15-a5db-dd7e-bc81-06bbef995e31@onenetbeyond.org> (raw)
In-Reply-To: <211109.864k8lvesb.gmgdl@evledraar.gmail.com>
Hi, sorry for delay reply. I was busy with some other works and couldn't
find the time to look into it.
On 11/9/21 9:42 AM, Ævar Arnfjörð Bjarmason wrote:
>
>> Thanks, I didn't know "reverse" would change the traversal order. When
>> I looked for "--reverse" option in git-log(1), this what I found:
>>
>> --reverse
>> Output the commits chosen to be shown (see Commit Limiting
>> section above) in reverse order. Cannot be combined with
>> --walk-reflogs.
>>
>> From this, I inferred that "--follow" would choose the commits and
>> "--reverse" reverses those commits order. Can we improve the wording
>> here? Especially, about "reverse" changes the traversing order.
>
> Yes, definitely. Suggestions most welcome :)
--reverse
Traverse the commits chosen to be shown (see Commit Limiting
section above) in reverse order. Cannot be combined with --walk-reflogs.
If we don't want to disallow combination of "--follow" and "--reverse",
just like "--walk-reflogs" as combination doesn't make any sense[1]. We
could do this:
--reverse
Traverse the commits chosen to be shown (see Commit Limiting
section above) in reverse order. Cannot be combined with --walk-reflogs.
Combination of --follow and --reverse won't produce an expected output,
if we also want to follow renames. If there is nothing to follow it
should behave as expected.
[1]:
https://public-inbox.org/git/6c6ef97c-9de5-176f-f328-c4dffd96d495@onenetbeyond.org/
Does it sound good to you?
-v
next prev parent reply other threads:[~2021-12-14 3:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 4:10 List all commits of a specified file in oldest to newest order Vipul Kumar
2021-11-05 8:13 ` Ævar Arnfjörð Bjarmason
2021-11-09 3:35 ` Vipul Kumar
2021-11-09 9:42 ` Ævar Arnfjörð Bjarmason
2021-12-14 3:58 ` Vipul Kumar [this message]
2021-11-05 8:17 ` Jeff King
2021-11-05 18:49 ` Junio C Hamano
2021-11-05 23:26 ` Jeff King
2021-11-09 5:24 ` Vipul Kumar
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=71d21b15-a5db-dd7e-bc81-06bbef995e31@onenetbeyond.org \
--to=kumar@onenetbeyond.org \
--cc=avarab@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).