Re: [PATCH] doc: fix capitalization in porcelain v2 section

2 messages, 2 authors, 2021-09-28 · open the first message on its own page

Re: [PATCH] doc: fix capitalization in porcelain v2 section

From: Junio C Hamano <hidden>
Date: 2021-09-27 20:12:14

"Orgad Shaneh via GitGitGadget" [off-list ref] writes:
Subject: Re: [PATCH] doc: fix capitalization in porcelain v2 section
From: Orgad Shaneh <redacted>
Between "doc" and "porcelain v2 section", there is this level called
"page" ;-) When this commit is mixed together with other commits in
"git shortlog" output, it will be hard to tell that this is about
fixing documentation for which command, so you must give it to your
readers.

    Subject: doc: match XY placeholder in status --porcelain-v2 output

or something like that, perhaps?

Thanks.
quoted hunk
The summary line had xy, while the description (and other sub-sections)
has XY.

Signed-off-by: Orgad Shaneh <redacted>
---
    doc: fix capitalization in porcelain v2 section
    
    The summary line had xy, while the description (and other sub-sections)
    has XY.
    
    Signed-off-by: Orgad Shaneh orgads@gmail.com

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1095%2Forgads%2Fstatus-doc-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1095/orgads/status-doc-v1
Pull-Request: https://github.com/git/git/pull/1095

 Documentation/git-status.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt
index 83f38e31981..c33a3d8d532 100644
--- a/Documentation/git-status.txt
+++ b/Documentation/git-status.txt
@@ -363,7 +363,7 @@ Field       Meaning
 Unmerged entries have the following format; the first character is
 a "u" to distinguish from ordinary changed entries.
 
-    u <xy> <sub> <m1> <m2> <m3> <mW> <h1> <h2> <h3> <path>
+    u <XY> <sub> <m1> <m2> <m3> <mW> <h1> <h2> <h3> <path>
 
 ....
 Field       Meaning
base-commit: ddb1055343948e0d0bc81f8d20245f1ada6430a0

Re: [PATCH] doc: fix capitalization in porcelain v2 section

From: Orgad Shaneh <hidden>
Date: 2021-09-28 20:42:37

On Mon, Sep 27, 2021 at 11:12 PM Junio C Hamano [off-list ref] wrote:
"Orgad Shaneh via GitGitGadget" [off-list ref] writes:
quoted
Subject: Re: [PATCH] doc: fix capitalization in porcelain v2 section
From: Orgad Shaneh <redacted>
Between "doc" and "porcelain v2 section", there is this level called
"page" ;-) When this commit is mixed together with other commits in
"git shortlog" output, it will be hard to tell that this is about
fixing documentation for which command, so you must give it to your
readers.

    Subject: doc: match XY placeholder in status --porcelain-v2 output

or something like that, perhaps?

Thanks.
quoted
The summary line had xy, while the description (and other sub-sections)
has XY.

Signed-off-by: Orgad Shaneh <redacted>
---
    doc: fix capitalization in porcelain v2 section

    The summary line had xy, while the description (and other sub-sections)
    has XY.

    Signed-off-by: Orgad Shaneh orgads@gmail.com

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1095%2Forgads%2Fstatus-doc-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1095/orgads/status-doc-v1
Pull-Request: https://github.com/git/git/pull/1095

 Documentation/git-status.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt
index 83f38e31981..c33a3d8d532 100644
--- a/Documentation/git-status.txt
+++ b/Documentation/git-status.txt
@@ -363,7 +363,7 @@ Field       Meaning
 Unmerged entries have the following format; the first character is
 a "u" to distinguish from ordinary changed entries.

-    u <xy> <sub> <m1> <m2> <m3> <mW> <h1> <h2> <h3> <path>
+    u <XY> <sub> <m1> <m2> <m3> <mW> <h1> <h2> <h3> <path>

 ....
 Field       Meaning
base-commit: ddb1055343948e0d0bc81f8d20245f1ada6430a0
Fine with me. Should I resubmit the patch, or will you push it with
the revised subject?

-  Orgad
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help