From: Junio C Hamano <gitster@pobox.com>
To: "Kai Koponen via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
Kai Koponen <kaikoponen@google.com>
Subject: Re: [PATCH] doc: mention rev-list --ancestry-path restrictions
Date: Wed, 04 Dec 2024 09:10:19 +0900 [thread overview]
Message-ID: <xmqqiks071g4.fsf@gitster.g> (raw)
In-Reply-To: <pull.1838.git.git.1733257083739.gitgitgadget@gmail.com> (Kai Koponen via GitGitGadget's message of "Tue, 03 Dec 2024 20:18:03 +0000")
"Kai Koponen via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Kai Koponen <kaikoponen@google.com>
>
> The rev-list documention doesn't mention that the given
> commit must be in the specified commit range, leading
> to unexpected results.
>
> Signed-off-by: Kai Koponen <kaikoponen@google.com>
> ---
> doc: mention rev-list --ancestry-path restrictions
Thanks.
next prev parent reply other threads:[~2024-12-04 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 20:18 [PATCH] doc: mention rev-list --ancestry-path restrictions Kai Koponen via GitGitGadget
2024-12-03 22:22 ` Elijah Newren
2024-12-04 0:10 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-19 21:53 rev-list --ancestry-path with arg - bug or undocumented requirement Kai Koponen
2024-11-20 3:22 ` Elijah Newren
2024-12-02 19:45 ` Kai Koponen
2024-12-03 1:05 ` Junio C Hamano
2024-12-03 17:14 ` [PATCH] doc: mention rev-list --ancestry-path restrictions Kai Koponen
2024-12-03 17:38 ` Kristoffer Haugsbakk
2024-12-03 17:59 ` Kai Koponen
2024-12-03 20:21 ` Kai Koponen
2024-12-03 23:33 ` Junio C Hamano
2024-12-03 23:36 ` Kai Koponen
2024-12-03 23:24 ` 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=xmqqiks071g4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=kaikoponen@google.com \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=newren@gmail.com \
/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).