doc: correct the 50 characters soft limit (+)
PATCH 1/1 doc: correct the 50 characters soft limit (+)
From: =?UTF-8?q?=E8=B0=A2=E8=87=B4=E9=82=A6=20=28XIE=20Zhibang=29?=
<[email protected]>
The soft limit of the first line of the commit message should be "no more than 50 characters" or "50 characters or less", but not "less than 50 character".
This is an addition to commit c2c349a15c0430a2ef9f858d69d095a00693379c ("doc: correct the 50 characters soft limit").
---
doc: correct the 50 characters soft limit (+)
The soft limit of the first line of the commit message should be "no more than 50 characters" or "50 characters or less", but not "less than 50 character".
This is an addition to commit c2c349a15c0430a2ef9f858d69d095a00693379c ("doc: correct the 50 characters soft limit").
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1585%2FRed54%2Fdoc-patch-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1585/Red54/doc-patch-v1
Pull-Request: https://github.com/git/git/pull/1585
Documentation/gittutorial.txt | 8 ++++---- Documentation/user-manual.txt | 2 +- po/README.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-)
Documentation/gittutorial.txt +4 -4
@@ -137,10 +137,10 @@ which will automatically notice any modified (but not new) files, add them to the index, and commit, all in one step. A note on commit messages: Though not required, it's a good idea to -begin the commit message with a single short (less than 50 character) -line summarizing the change, followed by a blank line and then a more -thorough description. The text up to the first blank line in a commit -message is treated as the commit title, and that title is used +begin the commit message with a single short (no more than 50 +characters) line summarizing the change, followed by a blank line and +then a more thorough description. The text up to the first blank line in +a commit message is treated as the commit title, and that title is used throughout Git. For example, linkgit:git-format-patch[1] turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body.
Documentation/user-manual.txt +1 -1
@@ -1122,7 +1122,7 @@ choosing "Stage Hunk For Commit"). === Creating good commit messages Though not required, it's a good idea to begin the commit message -with a single short (less than 50 character) line summarizing the +with a single short (no more than 50 characters) line summarizing the change, followed by a blank line and then a more thorough description. The text up to the first blank line in a commit message is treated as the commit title, and that title is used
po/README.md +1 -1
@@ -412,7 +412,7 @@ There are some conventions that l10n contributors must follow: - Do not use non-ASCII characters in the subject of a commit. - The length of commit subject (first line of the commit log) should - be less than 50 characters, and the length of other lines of the + be no more than 50 characters, and the length of other lines of the commit log should be no more than 72 characters. - Add "Signed-off-by" trailer to your commit log, like other commits
base-commit: 3a06386e314565108ad56a9bdb8f7b80ac52fb69
Signature · 1 line
gitgitgadget
Hi 謝致邦
Quoted 2 lines · 謝致邦 (XIE Zhibang) via GitGitGadget
This is an addition to commit
c2c349a15c0430a2ef9f858d69d095a00693379c("doc: correct the 50 characters soft limit").
I think the “reference” format is nice:
c2c349a15c (doc: correct the 50 characters soft limit, 2023-09-28)
See Documentation/SubmittingPatches at commit-reference.
Signature · 1 line
Kristoffer Haugsbakk
PATCH v2 1/1 doc: correct the 50 characters soft limit (+)
In reply to 謝致邦 (XIE Zhibang) via GitGitGadgetFrom: =?UTF-8?q?=E8=B0=A2=E8=87=B4=E9=82=A6=20=28XIE=20Zhibang=29?=
<[email protected]>
The soft limit of the first line of the commit message should be "no more than 50 characters" or "50 characters or less", but not "less than 50 character".
This is an addition to commit c2c349a15c (doc: correct the 50 characters soft limit, 2023-09-28).
---
doc: correct the 50 characters soft limit (+)
The soft limit of the first line of the commit message should be "no more than 50 characters" or "50 characters or less", but not "less than 50 character".
This is an addition to commit c2c349a15c (doc: correct the 50 characters soft limit, 2023-09-28).
Change commit reference format, thank Kristoffer Haugsbakk.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1585%2FRed54%2Fdoc-patch-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1585/Red54/doc-patch-v2
Pull-Request: https://github.com/git/git/pull/1585
Range-diff vs v1:
1: 5b750bdf471 ! 1: 1808fcc3727 doc: correct the 50 characters soft limit (+)
@@ Commit message
"no more than 50 characters" or "50 characters or less", but not "less than 50 character".
- This is an addition to commit c2c349a15c0430a2ef9f858d69d095a00693379c
- ("doc: correct the 50 characters soft limit").
+ This is an addition to commit c2c349a15c (doc: correct the 50 characters
+ soft limit, 2023-09-28).
Documentation/gittutorial.txt | 8 ++++---- Documentation/user-manual.txt | 2 +- po/README.md | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-)
Documentation/gittutorial.txt +4 -4
@@ -137,10 +137,10 @@ which will automatically notice any modified (but not new) files, add them to the index, and commit, all in one step. A note on commit messages: Though not required, it's a good idea to -begin the commit message with a single short (less than 50 character) -line summarizing the change, followed by a blank line and then a more -thorough description. The text up to the first blank line in a commit -message is treated as the commit title, and that title is used +begin the commit message with a single short (no more than 50 +characters) line summarizing the change, followed by a blank line and +then a more thorough description. The text up to the first blank line in +a commit message is treated as the commit title, and that title is used throughout Git. For example, linkgit:git-format-patch[1] turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body.
Documentation/user-manual.txt +1 -1
@@ -1122,7 +1122,7 @@ choosing "Stage Hunk For Commit"). === Creating good commit messages Though not required, it's a good idea to begin the commit message -with a single short (less than 50 character) line summarizing the +with a single short (no more than 50 characters) line summarizing the change, followed by a blank line and then a more thorough description. The text up to the first blank line in a commit message is treated as the commit title, and that title is used
po/README.md +1 -1
@@ -412,7 +412,7 @@ There are some conventions that l10n contributors must follow: - Do not use non-ASCII characters in the subject of a commit. - The length of commit subject (first line of the commit log) should - be less than 50 characters, and the length of other lines of the + be no more than 50 characters, and the length of other lines of the commit log should be no more than 72 characters. - Add "Signed-off-by" trailer to your commit log, like other commits
base-commit: 3a06386e314565108ad56a9bdb8f7b80ac52fb69
Signature · 1 line
gitgitgadget