From: "squeaky" <334eevw4vj@liamekaens.com>
To: git@vger.kernel.org
Subject: git rev-list --no-walk RANGE not working as documented
Date: Mon, 20 Feb 2023 23:54:11 +0000 [thread overview]
Message-ID: <24417-1676937251-531825@sneakemail.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
git rev-list HERE..THERE --no-walk
What did you expect to happen? (Expected behavior)
Show the commits between HERE and THERE.
What happened instead? (Actual behavior)
Only THERE is shown.
What's different between what you expected and what actually happened?
The documentation for --no-walk says, "This has no effect if a range is specified."
Since HERE..THERE is a range, --no-walk should have no effect. This isn't working as documented.
Anything else you want to add:
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.39.2.501.gd9d677b2d8
cpu: x86_64
built from commit: d9d677b2d8cc5f70499db04e633ba7a400f64cbf
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 6.1.6-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Jan 14 16:55:06 UTC 2023 x86_64
compiler info: gnuc: 12.2
libc info: glibc: 2.36
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
[root@xps git]
next reply other threads:[~2023-02-21 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 23:54 squeaky [this message]
2024-10-01 15:04 ` git rev-list --no-walk RANGE not working as documented Kristoffer Haugsbakk
2024-10-02 19:18 ` 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=24417-1676937251-531825@sneakemail.com \
--to=334eevw4vj@liamekaens.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).