doc: convert fetch pull push to synopsis style#2002
doc: convert fetch pull push to synopsis style#2002jnavila wants to merge 3 commits intogitgitgadget:masterfrom
Conversation
c3667ba to
e5526ea
Compare
|
/submit |
|
Submitted as pull.2002.git.1763588404.gitgitgadget@gmail.com To fetch this version into To fetch this version to local tag |
|
This patch series was integrated into seen via git@522de41. |
|
This patch series was integrated into seen via git@9ac6ac4. |
|
This branch is now known as |
|
This patch series was integrated into seen via git@d121cd9. |
|
This patch series was integrated into next via git@eb9c170. |
|
This patch series was integrated into seen via git@52f29f9. |
|
There was a status update in the "New Topics" section about the branch Doc mark-up updates. Will merge to 'master'. source: <pull.2002.git.1763588404.gitgitgadget@gmail.com> |
- Switch the synopsis to a synopsis block which will automatically format placeholders in italics and keywords in monospace - Use _<placeholder>_ instead of <placeholder> in the description - Use `backticks` for keywords and more complex option descriptions. The new rendering engine will apply synopsis rules to these spans. Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
- Switch the synopsis to a synopsis block which will automatically format placeholders in italics and keywords in monospace - Use _<placeholder>_ instead of <placeholder> in the description - Use `backticks` for keywords and more complex option descriptions. The new rendering engine will apply synopsis rules to these spans. Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
- Switch the synopsis to a synopsis block which will automatically format placeholders in italics and keywords in monospace - Use _<placeholder>_ instead of <placeholder> in the description - Use `backticks` for keywords and more complex option descriptions. The new rendering engine will apply synopsis rules to these spans. Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
e5526ea to
9c70b34
Compare
|
/submit |
|
Submitted as pull.2002.v2.git.1763988532.gitgitgadget@gmail.com To fetch this version into To fetch this version to local tag |
|
On the Git mailing list, Junio C Hamano wrote (reply to this): "Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com> writes:
> 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 |
|
This patch series was integrated into seen via git@a7e4ba4. |
|
This patch series was integrated into seen via git@1867c6d. |
|
This patch series was integrated into seen via git@fae8be5. |
|
There was a status update in the "Cooking" section about the branch Doc mark-up updates. Will merge to 'master'. source: <pull.2002.git.1763588404.gitgitgadget@gmail.com> |
|
This patch series was integrated into seen via git@b7c98fa. |
|
There was a status update in the "Cooking" section about the branch Doc mark-up updates. Will merge to 'master'. source: <pull.2002.git.1763588404.gitgitgadget@gmail.com> |
|
This patch series was integrated into seen via git@ffd9bb1. |
|
This patch series was integrated into master via git@ffd9bb1. |
|
Closed via ffd9bb1. |
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).