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 v2 0/3] doc: convert fetch pull push to synopsis style
Date: Mon, 24 Nov 2025 12:48:49 +0000 [thread overview]
Message-ID: <pull.2002.v2.git.1763988532.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2002.git.1763588404.gitgitgadget@gmail.com>
This is the continuity of the conversion to the synopsis style with a few
additional formatting changes.
Change since V1: While proofreading again, I found a typo (extraneous
underscore character).
Jean-Noël Avila (3):
doc: convert git fetch to synopsis style
doc: convert git pull to synopsis style
doc: convert git push to synopsis style
Documentation/config/fetch.adoc | 60 +++----
Documentation/config/push.adoc | 113 ++++++------
Documentation/fetch-options.adoc | 211 +++++++++++-----------
Documentation/git-fetch.adoc | 48 ++---
Documentation/git-pull.adoc | 61 ++++---
Documentation/git-push.adoc | 267 +++++++++++++++-------------
Documentation/merge-options.adoc | 2 +-
Documentation/pull-fetch-param.adoc | 50 +++---
Documentation/urls-remotes.adoc | 18 +-
builtin/fetch.c | 2 +-
10 files changed, 427 insertions(+), 405 deletions(-)
base-commit: fd372d9b1a69a01a676398882bbe3840bf51fe72
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-2002%2Fjnavila%2Fdoc_git_fetch-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2002/jnavila/doc_git_fetch-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/2002
Range-diff vs v1:
1: 397f56d874 ! 1: 994f6ee414 doc: convert git fetch to synopsis style
@@ Documentation/pull-fetch-param.adoc: namespace it's being fetched to, the type o
+
Until Git version 2.20, and unlike when pushing with
linkgit:git-push[1], any updates to `refs/tags/*` would be accepted
-@@ Documentation/pull-fetch-param.adoc: object.
- When the remote branch you want to fetch is known to
- be rewound and rebased regularly, it is expected that
- its new tip will not be a descendant of its previous tip
--(as stored in your remote-tracking branch the last time
-+(as stored in your remote-tracking branch the last time_
- you fetched). You would want
- to use the `+` sign to indicate non-fast-forward updates
- will be needed for such branches. There is no way to
@@ Documentation/pull-fetch-param.adoc: must know this is the expected usage pattern for a branch.
ifdef::git-pull[]
+
2: 5b1e64bdf8 = 2: 6e9ea10311 doc: convert git pull to synopsis style
3: e5526eaf58 = 3: 9c70b341bb doc: convert git push to synopsis style
--
gitgitgadget
next prev parent reply other threads:[~2025-11-24 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 21:40 [PATCH 0/3] doc: convert fetch pull push to synopsis style Jean-Noël Avila via GitGitGadget
2025-11-19 21:40 ` [PATCH 1/3] doc: convert git fetch " Jean-Noël Avila via GitGitGadget
2025-11-19 21:40 ` [PATCH 2/3] doc: convert git pull " Jean-Noël Avila via GitGitGadget
2025-11-19 21:40 ` [PATCH 3/3] doc: convert git push " Jean-Noël Avila via GitGitGadget
2025-11-24 12:48 ` Jean-Noël Avila via GitGitGadget [this message]
2025-11-24 12:48 ` [PATCH v2 1/3] doc: convert git fetch " Jean-Noël Avila via GitGitGadget
2025-11-24 12:48 ` [PATCH v2 2/3] doc: convert git pull " Jean-Noël Avila via GitGitGadget
2025-11-24 12:48 ` [PATCH v2 3/3] doc: convert git push " Jean-Noël Avila via GitGitGadget
2025-11-24 18:14 ` [PATCH v2 0/3] doc: convert fetch pull " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.2002.v2.git.1763988532.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).