All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Pavel Rappo <pavel.rappo@gmail.com>,
	 Git mailing list <git@vger.kernel.org>
Subject: Re: Determining if a merge was produced automatically
Date: Mon, 01 Jul 2024 08:43:45 -0700	[thread overview]
Message-ID: <xmqqh6d9yv66.fsf@gitster.g> (raw)
In-Reply-To: <ZoKXt0jPphoM5nmJ@google.com> (Jonathan Nieder's message of "Mon, 1 Jul 2024 13:49:11 +0200")

Jonathan Nieder <jrnieder@gmail.com> writes:

>> 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.

I do not think that was what Pavel wanted to get suggestion on, but
it is certainly something that would benefit not just a single
person but other users ;-)

  parent reply	other threads:[~2024-07-01 15:43 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
2024-07-01 13:13   ` Pavel Rappo
2024-07-01 15:43   ` Junio C Hamano [this message]
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=xmqqh6d9yv66.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --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 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.