From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Fernando Ramos <greenfoo@u92.eu>, git@vger.kernel.org
Cc: gitster@pobox.com, davvid@gmail.com, sunshine@sunshineco.com,
seth@eseth.com, levraiphilippeblain@gmail.com,
rogi@skylittlesystem.org
Subject: Re: [PATCH v6 3/3] vimdiff: add tool documentation
Date: Mon, 28 Mar 2022 11:48:08 +0700 [thread overview]
Message-ID: <2d1b3c6d-4345-8b7d-b8b8-4baf1edd91f0@gmail.com> (raw)
In-Reply-To: <20220327112307.151044-4-greenfoo@u92.eu>
On 27/03/22 18.23, Fernando Ramos wrote:
> +When using these variants, in order to specify a custom layout you will have to
> +set configuration variables `mergetool.gvimdiff.layout` and
> +`mergetool.nvimdiff.layout` instead of `mergetool.vimdiff.layout`
> +
What about this wording?
"These variants also have corresponding layout configuration named
`mergetool.gvimdiff.layout` and `mergetool.nvimdiff.layout`, respectively."
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-03-28 4:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 11:23 [PATCH v6 0/3] vimdiff: new implementation with layout support Fernando Ramos
2022-03-27 11:23 ` [PATCH v6 1/3] " Fernando Ramos
2022-03-27 16:47 ` Philippe Blain
2022-03-27 18:12 ` Fernando Ramos
2022-03-27 21:36 ` Junio C Hamano
2022-03-27 11:23 ` [PATCH v6 2/3] vimdiff: integrate layout tests in the unit tests framework ('t' folder) Fernando Ramos
2022-03-27 21:37 ` Junio C Hamano
2022-03-27 11:23 ` [PATCH v6 3/3] vimdiff: add tool documentation Fernando Ramos
2022-03-27 18:28 ` Philippe Blain
2022-03-27 18:50 ` [PATCH] fixup! " Philippe Blain
2022-03-27 21:10 ` [PATCH v6 3/3] " Fernando Ramos
2022-03-27 21:43 ` Junio C Hamano
2022-03-27 22:17 ` Fernando Ramos
2022-03-28 4:48 ` Bagas Sanjaya [this message]
2022-03-28 5:43 ` Junio C Hamano
2022-03-28 19:19 ` Fernando Ramos
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=2d1b3c6d-4345-8b7d-b8b8-4baf1edd91f0@gmail.com \
--to=bagasdotme@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=greenfoo@u92.eu \
--cc=levraiphilippeblain@gmail.com \
--cc=rogi@skylittlesystem.org \
--cc=seth@eseth.com \
--cc=sunshine@sunshineco.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.
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).