git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Jean-Noël Avila" <jn.avila@free.fr>
Subject: [PATCH 0/9] doc: convert checkout, switch and merge to new format
Date: Sun, 25 May 2025 20:27:00 +0000	[thread overview]
Message-ID: <pull.1927.git.1748204829.gitgitgadget@gmail.com> (raw)

This is the follow-up in the conversion of the manpages to the synopsis
style.

This time, we address git checkout, git switch, git merge and git mergetool.

I added a small grammatical fixup in merge options.

Jean-Noël Avila (9):
  doc: convert git-checkout manpage to new style
  doc: convert git-merge manpage to new style
  doc: convert merge options to new synopsis format
  doc: merge-options.adoc remove a misleading double negation
  doc: convert merge strategies to synopsis format
  doc: switch merge config description to new synopsis format
  doc: convert git-mergetool manpage to new synopsis style
  doc: convert git-mergetool options to new synopsis style
  doc: convert git-switch manpage to new synopsis style

 Documentation/config/checkout.adoc      |  14 +-
 Documentation/config/fmt-merge-msg.adoc |   8 +-
 Documentation/config/merge.adoc         |  84 ++++-----
 Documentation/config/mergetool.adoc     |  54 +++---
 Documentation/git-checkout.adoc         | 228 ++++++++++++------------
 Documentation/git-merge.adoc            |  51 +++---
 Documentation/git-mergetool.adoc        |  62 +++----
 Documentation/git-switch.adoc           | 114 ++++++------
 Documentation/merge-options.adoc        | 110 ++++++------
 Documentation/merge-strategies.adoc     |  58 +++---
 Documentation/mergetools/vimdiff.adoc   |  16 +-
 Documentation/rerere-options.adoc       |   4 +-
 12 files changed, 403 insertions(+), 400 deletions(-)


base-commit: 845c48a16a7f7b2c44d8cb137b16a4a1f0140229
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1927%2Fjnavila%2Fcheckout_merge-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1927/jnavila/checkout_merge-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1927
-- 
gitgitgadget

             reply	other threads:[~2025-05-25 20:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25 20:27 Jean-Noël Avila via GitGitGadget [this message]
2025-05-25 20:27 ` [PATCH 1/9] doc: convert git-checkout manpage to new style Jean-Noël Avila via GitGitGadget
2025-05-25 20:27 ` [PATCH 2/9] doc: convert git-merge " Jean-Noël Avila via GitGitGadget
2025-05-25 20:27 ` [PATCH 3/9] doc: convert merge options to new synopsis format Jean-Noël Avila via GitGitGadget
2025-05-25 20:27 ` [PATCH 4/9] doc: merge-options.adoc remove a misleading double negation Jean-Noël Avila via GitGitGadget
2025-05-25 20:27 ` [PATCH 5/9] doc: convert merge strategies to synopsis format Jean-Noël Avila via GitGitGadget
2025-05-25 20:27 ` [PATCH 6/9] doc: switch merge config description to new " Jean-Noël Avila via GitGitGadget
2025-05-25 20:27 ` [PATCH 7/9] doc: convert git-mergetool manpage to new synopsis style Jean-Noël Avila via GitGitGadget
2025-05-25 20:27 ` [PATCH 8/9] doc: convert git-mergetool options " Jean-Noël Avila via GitGitGadget
2025-05-25 20:27 ` [PATCH 9/9] doc: convert git-switch manpage " Jean-Noël Avila via GitGitGadget

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=pull.1927.git.1748204829.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jn.avila@free.fr \
    /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).