Re: [PATCH] Documentation: GPG capitalization

2 messages, 2 authors, 2016-06-16 · open the first message on its own page

Re: [PATCH] Documentation: GPG capitalization

From: Junio C Hamano <hidden>
Date: 2016-06-16 02:19:39

Dave Nicolson [off-list ref] writes:
quoted hunk
When "GPG" is used in a sentence it is now consistently capitalized. When referring to the binary it is left as "gpg".

Signed-off-by: David Nicolson <redacted>
---
 Documentation/git-mktag.txt         | 2 +-
 Documentation/git-tag.txt           | 2 +-
 Documentation/git-verify-commit.txt | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-mktag.txt b/Documentation/git-mktag.txt
index fa6a756..724408d 100644
--- a/Documentation/git-mktag.txt
+++ b/Documentation/git-mktag.txt
@@ -32,7 +32,7 @@ followed by some 'optional' free-form message (some tags created
 by older Git may not have `tagger` line).  The message, when
 exists, is separated by a blank line from the header.  The
 message part may contain a signature that Git itself doesn't
-care about, but that can be verified with gpg.
+care about, but that can be verified with GPG.
Isn't this a name of the program, though?  Other two hunks in your
patch clearly refer to the concept and not to a particular program,
and they are good changes, I think.
quoted hunk
 
 GIT
 ---
diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
index abab481..32bc4aa 100644
--- a/Documentation/git-tag.txt
+++ b/Documentation/git-tag.txt
@@ -78,7 +78,7 @@ OPTIONS
 
 -v::
 --verify::
-	Verify the gpg signature of the given tag names.
+	Verify the GPG signature of the given tag names.
 
 -n<num>::
 	<num> specifies how many lines from the annotation, if any,
diff --git a/Documentation/git-verify-commit.txt b/Documentation/git-verify-commit.txt
index ecf4da1..0101f0f 100644
--- a/Documentation/git-verify-commit.txt
+++ b/Documentation/git-verify-commit.txt
@@ -12,12 +12,12 @@ SYNOPSIS
 
 DESCRIPTION
 -----------
-Validates the gpg signature created by 'git commit -S'.
+Validates the GPG signature created by 'git commit -S'.
 
 OPTIONS
 -------
 --raw::
-	Print the raw gpg status output to standard error instead of the normal
+	Print the raw GPG status output to standard error instead of the normal
 	human-readable output.
 
 -v::

--
https://github.com/git/git/pull/246

Re: [PATCH] Documentation: GPG capitalization

From: David Nicolson <hidden>
Date: 2016-06-16 02:19:39

On Mon, May 30, 2016 at 8:02 PM, Junio C Hamano [off-list ref] wrote:
Dave Nicolson [off-list ref] writes:
quoted
When "GPG" is used in a sentence it is now consistently capitalized. When referring to the binary it is left as "gpg".

Signed-off-by: David Nicolson <redacted>
---
 Documentation/git-mktag.txt         | 2 +-
 Documentation/git-tag.txt           | 2 +-
 Documentation/git-verify-commit.txt | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-mktag.txt b/Documentation/git-mktag.txt
index fa6a756..724408d 100644
--- a/Documentation/git-mktag.txt
+++ b/Documentation/git-mktag.txt
@@ -32,7 +32,7 @@ followed by some 'optional' free-form message (some tags created
 by older Git may not have `tagger` line).  The message, when
 exists, is separated by a blank line from the header.  The
 message part may contain a signature that Git itself doesn't
-care about, but that can be verified with gpg.
+care about, but that can be verified with GPG.
Isn't this a name of the program, though?  Other two hunks in your
patch clearly refer to the concept and not to a particular program,
and they are good changes, I think.
This one was not as clear as the other hunks. Git is referred to as
"Git" in the preceding line, which in itself could be referring to the
concept or the particular program I guess?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help