From: Jonathan Nieder <jrnieder@gmail.com>
To: Pavel Rappo <pavel.rappo@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: Determining if a merge was produced automatically
Date: Mon, 1 Jul 2024 13:49:11 +0200 [thread overview]
Message-ID: <ZoKXt0jPphoM5nmJ@google.com> (raw)
In-Reply-To: <CAChcVu=Kwqj7JhXqQW6Ni9+3TdSfdmHfSTJQWm1_uO2kczSm8g@mail.gmail.com>
Hi Pavel,
Pavel Rappo wrote:
> However, this bit means that I shouldn't entirely trust its output:
>
>> The output emitted when this option is used is subject to change, and so is its interaction with other options (unless explicitly documented).
>
> What is my best course of action?
I'd encourage proposing a patch to make the documentation say what you
wish it said. What guarantees would you like it to make? That will
help with others in the project being able to decide what it should
guarantee and what it shouldn't, and regardless of the outcome of
discussion it would make the documentation more helpful for the next
person.
See Documentation/MyFirstContribution for some more details on how
proposing a patch works.
Thanks and hope that helps,
Jonathan
next prev parent reply other threads:[~2024-07-01 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 18:06 Determining if a merge was produced automatically Pavel Rappo
[not found] ` <CANiSa6hVbrCpPtBCL_W8+43uWGL0LFJkFhSJYGtfFgxX75zE8w@mail.gmail.com>
2024-07-01 0:45 ` Martin von Zweigbergk
2024-07-01 15:11 ` Elijah Newren
2024-07-01 16:43 ` Pavel Rappo
2024-07-01 11:49 ` Jonathan Nieder [this message]
2024-07-01 13:13 ` Pavel Rappo
2024-07-01 15:43 ` Junio C Hamano
2024-07-01 15:39 ` Junio C Hamano
2024-07-01 16:08 ` Pavel Rappo
2024-07-01 18:16 ` Junio C Hamano
2024-07-01 22:26 ` Pavel Rappo
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=ZoKXt0jPphoM5nmJ@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=pavel.rappo@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).