From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Fernando Ramos <greenfoo@u92.eu>
Subject: fr/vimdiff-layout (was: What's cooking in git.git (Mar 2022, #05; Wed, 23))
Date: Sat, 26 Mar 2022 17:05:58 +0100 [thread overview]
Message-ID: <220326.86k0cgk83t.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqwngkm4am.fsf@gitster.g>
On Wed, Mar 23 2022, Junio C Hamano wrote:
> * fr/vimdiff-layout (2022-03-23) 3 commits
> - vimdiff: integrate layout tests in the unit tests framework ('t' folder)
> - vimdiff: add tool documentation
> - vimdiff: new implementation with layout support
>
> Reimplement "vimdiff[123]" mergetool drivers with a more generic
> layout mechanism.
>
> Will merge to 'next'?
> source: <20220319091141.4911-1-greenfoo@u92.eu>
It looks like it's emitting a new warning from the "Makefile" in
check-docs:
$ (make clean && make check-docs) >/dev/null 2>&1; make check-docs
make -C Documentation lint-docs
make[1]: Entering directory '/home/avar/g/git/Documentation'
make[1]: Nothing to be done for 'lint-docs'.
make[1]: Leaving directory '/home/avar/g/git/Documentation'
removed but documented: git-difftool--vimdiff
removed but documented: git-mergetool--vimdiff
removed but documented: git-version
Re https://lore.kernel.org/git/87o88i2keu.fsf@evledraar.gmail.com/ I
haven't checked if this is the same case of a thing we should just
ignore, or if it's raising an actual issue this time.
next prev parent reply other threads:[~2022-03-26 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 3:13 What's cooking in git.git (Mar 2022, #05; Wed, 23) Junio C Hamano
2022-03-25 13:38 ` ab/commit-plug-leaks (was: What's cooking in git.git (Mar 2022, #05; Wed, 23)) Ævar Arnfjörð Bjarmason
2022-03-26 16:05 ` Ævar Arnfjörð Bjarmason [this message]
2022-03-26 22:55 ` fr/vimdiff-layout " Fernando Ramos
2022-03-27 0:29 ` fr/vimdiff-layout Junio C Hamano
2022-03-27 13:18 ` [PATCH] tests: do roundtrip builtin doc & sanity checking Ævar Arnfjörð Bjarmason
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=220326.86k0cgk83t.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=greenfoo@u92.eu \
/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).