git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Phillip Wood <phillip.wood@dunelm.org.uk>
Cc: Git Mailing List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 4/4] merge: tweak --rerere-autoupdate documentation
Date: Wed, 13 Mar 2019 23:57:31 +0100 (STD)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1903132357070.41@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20190313182756.8076-4-phillip.wood123@gmail.com>

Hi Phillip,

On Wed, 13 Mar 2019, Phillip Wood wrote:

> From: Phillip Wood <phillip.wood@dunelm.org.uk>
> 
> Spell out --no-rerere-autoupdate explictly to make searching
> easier. This matches the other --no options in the man page.
> 
> Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
> ---
>  Documentation/git-merge.txt | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/git-merge.txt b/Documentation/git-merge.txt
> index 4cc86469f3..6294dbc09d 100644
> --- a/Documentation/git-merge.txt
> +++ b/Documentation/git-merge.txt
> @@ -83,7 +83,8 @@ invocations. The automated message can include the branch description.
>  If `--log` is specified, a shortlog of the commits being merged
>  will be appended to the specified message.
>  
> ---[no-]rerere-autoupdate::
> +--rerere-autoupdate::
> +--no-rerere-autoupdate::
>  	Allow the rerere mechanism to update the index with the
>  	result of auto-conflict resolution if possible.

All four patches make sense to me.

Thanks,
Dscho

  reply	other threads:[~2019-03-13 22:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 18:27 [PATCH 1/4] rebase: document --rerere-autoupdate Phillip Wood
2019-03-13 18:27 ` [PATCH 2/4] cherry-pick/revert: " Phillip Wood
2019-03-13 18:27 ` [PATCH 3/4] am: " Phillip Wood
2019-03-13 18:27 ` [PATCH 4/4] merge: tweak --rerere-autoupdate documentation Phillip Wood
2019-03-13 22:57   ` Johannes Schindelin [this message]
2019-03-14  5:05 ` [PATCH 1/4] rebase: document --rerere-autoupdate Junio C Hamano
2019-03-14 19:12   ` am/cherry-pick/rebase/revert: " Phillip Wood
2019-03-14 19:12     ` [PATCH v2 1/2] " Phillip Wood
2019-03-14 19:12     ` [PATCH v2 2/2] merge: tweak --rerere-autoupdate documentation Phillip Wood
2019-03-18  1:25     ` am/cherry-pick/rebase/revert: document --rerere-autoupdate 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

  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=nycvar.QRO.7.76.6.1903132357070.41@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=phillip.wood@dunelm.org.uk \
    /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).