git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 0/3] doc: convert fetch pull push to synopsis style

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 24, 2025, 18:14 UTC
Message-ID
<xmqqy0nvxppo.fsf@gitster.g>
In-Reply-To
<pull.2002.v2.git.1763988532.gitgitgadget@gmail.com>
"Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 18 quoted lines
> 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[]

Ah, this was a spurious change that did not need to exist there, and this round removes the whole thing. Looks good.

>  2:  5b1e64bdf8 = 2:  6e9ea10311 doc: convert git pull to synopsis style
>  3:  e5526eaf58 = 3:  9c70b341bb doc: convert git push to synopsis style
Previous: Jean-Noël Avila via GitGitGadget
Message 9 of 9 in “doc: convert fetch pull push to synopsis style”
  1. 0/3 doc: convert fetch pull push to synopsis styleJean-Noël Avila via GitGitGadget, Nov 19, 2025
  2. 2/3 doc: convert git pull to synopsis styleJean-Noël Avila via GitGitGadget, Nov 19, 2025
  3. 1/3 doc: convert git fetch to synopsis styleJean-Noël Avila via GitGitGadget, Nov 19, 2025
  4. 3/3 doc: convert git push to synopsis styleJean-Noël Avila via GitGitGadget, Nov 19, 2025
  5. 0/3 doc: convert fetch pull push to synopsis styleJean-Noël Avila via GitGitGadget, Nov 24, 2025
  6. 1/3 doc: convert git fetch to synopsis styleJean-Noël Avila via GitGitGadget, Nov 24, 2025
  7. 2/3 doc: convert git pull to synopsis styleJean-Noël Avila via GitGitGadget, Nov 24, 2025
  8. 3/3 doc: convert git push to synopsis styleJean-Noël Avila via GitGitGadget, Nov 24, 2025
  9. Junio C HamanoNov 24, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.