{"thread":{"id":"31521","subject":"[PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","startedAt":"2012-09-13T12:42:08Z","lastAt":"2012-09-13T22:25:21Z","messageCount":8,"participants":["Jeremy White","Junio C Hamano","Philip Oakley"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"198912","messageId":"5051D4A0.4060608@codeweavers.com","threadId":"31521","inReplyTo":null,"subject":"[PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","fromName":"Jeremy White","fromEmail":"jwhite@codeweavers.com","sentAt":"2012-09-13T12:42:08Z","receivedAt":"2012-09-13T12:42:08Z","isPatch":true,"sender":{"key":"jwhite@codeweavers.com","avatar":"https://avatars.githubusercontent.com/u/1063742?v=4"},"body":"The discussion of email subject throughout the documentation is\nmisleading; it indicates that the first line will become the subject.\nIn fact, the first and second and third lines will become the subject,\nup until the first full blank line.  Describing it as the first paragraph\nis more accurate.\n\nSigned-off-by: Jeremy White <jwhite@codeweavers.com>\n---\n Documentation/git-commit.txt       |    2 +-\n Documentation/git-for-each-ref.txt |    2 +-\n Documentation/git-format-patch.txt |    8 +++++---\n Documentation/git-shortlog.txt     |    2 +-\n Documentation/gitcore-tutorial.txt |    2 +-\n Documentation/gittutorial.txt      |    2 +-\n Documentation/user-manual.txt      |    2 +-\n 7 files changed, 11 insertions(+), 9 deletions(-)\n\ndiff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\nindex e99bb14..a61bca9 100644\n--- a/Documentation/git-commit.txt\n+++ b/Documentation/git-commit.txt\n@@ -349,7 +349,7 @@ DISCUSSION\n Though not required, it's a good idea to begin the commit message\n with a single short (less than 50 character) line summarizing the\n change, followed by a blank line and then a more thorough description.\n-Tools that turn commits into email, for example, use the first line\n+Tools that turn commits into email, for example, use the first paragraph\n on the Subject: line and the rest of the commit in the body.\n \n include::i18n.txt[]\ndiff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\nindex 7e83288..499c26a 100644\n--- a/Documentation/git-for-each-ref.txt\n+++ b/Documentation/git-for-each-ref.txt\n@@ -100,7 +100,7 @@ Fields that have name-email-date tuple as its value (`author`,\n `committer`, and `tagger`) can be suffixed with `name`, `email`,\n and `date` to extract the named component.\n \n-The first line of the message in a commit and tag object is\n+The first paragraph of the message in a commit and tag object is\n `subject`, the remaining lines are `body`.  The whole message\n is `contents`.\n \ndiff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt\nindex 9674f9d..e6f6d0e 100644\n--- a/Documentation/git-format-patch.txt\n+++ b/Documentation/git-format-patch.txt\n@@ -57,10 +57,12 @@ output, unless the `--stdout` option is specified.\n If `-o` is specified, output files are created in <dir>.  Otherwise\n they are created in the current working directory.\n \n-By default, the subject of a single patch is \"[PATCH] First Line\" and\n+By default, the subject of a single patch is \"[PATCH] First Paragraph\" and\n the subject when multiple patches are output is \"[PATCH n/m] First\n-Line\". To force 1/1 to be added for a single patch, use `-n`.  To omit\n-patch numbers from the subject, use `-N`.\n+Paragraph\". Note that \"First Paragraph\" consists of text in the commit message\n+prior to the first completely blank line (see the DISCUSSION section\n+in linkgit:git-commit[1]).  To force 1/1 to be added for a single patch,\n+use `-n`.  To omit patch numbers from the subject, use `-N`.\n \n If given `--thread`, `git-format-patch` will generate `In-Reply-To` and\n `References` headers to make the second and subsequent patch mails appear\ndiff --git a/Documentation/git-shortlog.txt b/Documentation/git-shortlog.txt\nindex dfd4d0c..9464932 100644\n--- a/Documentation/git-shortlog.txt\n+++ b/Documentation/git-shortlog.txt\n@@ -15,7 +15,7 @@ DESCRIPTION\n -----------\n Summarizes 'git log' output in a format suitable for inclusion\n in release announcements. Each commit will be grouped by author and\n-the first line of the commit message will be shown.\n+the first paragraph of the commit message will be shown.\n \n Additionally, \"[PATCH]\" will be stripped from the commit description.\n \ndiff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt\nindex f7815e9..92f97e6 100644\n--- a/Documentation/gitcore-tutorial.txt\n+++ b/Documentation/gitcore-tutorial.txt\n@@ -956,7 +956,7 @@ $ git show-branch --topo-order --more=1 master mybranch\n ------------------------------------------------\n \n The first two lines indicate that it is showing the two branches\n-and the first line of the commit log message from their\n+and the first paragraph of the commit log message from their\n top-of-the-tree commits, you are currently on `master` branch\n (notice the asterisk `\\*` character), and the first column for\n the later output lines is used to show commits contained in the\ndiff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt\nindex 1c16066..a1bc56c 100644\n--- a/Documentation/gittutorial.txt\n+++ b/Documentation/gittutorial.txt\n@@ -139,7 +139,7 @@ A note on commit messages: Though not required, it's a good idea to\n begin the commit message with a single short (less than 50 character)\n line summarizing the change, followed by a blank line and then a more\n thorough description.  Tools that turn commits into email, for\n-example, use the first line on the Subject: line and the rest of the\n+example, use the first paragraph on the Subject: line and the rest of the\n commit in the body.\n \n Git tracks content not files\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex fe6fb72..dd2f985 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -1126,7 +1126,7 @@ Though not required, it's a good idea to begin the commit message\n with a single short (less than 50 character) line summarizing the\n change, followed by a blank line and then a more thorough\n description.  Tools that turn commits into email, for example, use\n-the first line on the Subject line and the rest of the commit in the\n+the first paragraph on the Subject line and the rest of the commit in the\n body.\n \n [[ignoring-files]]\n-- \n1.7.9.5\n"},{"id":"198948","messageId":"7vehm593v8.fsf@alter.siamese.dyndns.org","threadId":"31521","inReplyTo":"5051D4A0.4060608@codeweavers.com","subject":"Re: [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-09-13T18:25:47Z","receivedAt":"2012-09-13T18:25:47Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeremy White <jwhite@codeweavers.com> writes:\n\n> The discussion of email subject throughout the documentation is\n> misleading; it indicates that the first line will become the subject.\n> In fact, the first and second and third lines will become the subject,\n> up until the first full blank line.  Describing it as the first paragraph\n> is more accurate.\n>\n> Signed-off-by: Jeremy White <jwhite@codeweavers.com>\n> ---\n>  Documentation/git-commit.txt       |    2 +-\n>  Documentation/git-for-each-ref.txt |    2 +-\n>  Documentation/git-format-patch.txt |    8 +++++---\n>  Documentation/git-shortlog.txt     |    2 +-\n>  Documentation/gitcore-tutorial.txt |    2 +-\n>  Documentation/gittutorial.txt      |    2 +-\n>  Documentation/user-manual.txt      |    2 +-\n>  7 files changed, 11 insertions(+), 9 deletions(-)\n>\n> diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt\n> index e99bb14..a61bca9 100644\n> --- a/Documentation/git-commit.txt\n> +++ b/Documentation/git-commit.txt\n> @@ -349,7 +349,7 @@ DISCUSSION\n>  Though not required, it's a good idea to begin the commit message\n>  with a single short (less than 50 character) line summarizing the\n>  change, followed by a blank line and then a more thorough description.\n> -Tools that turn commits into email, for example, use the first line\n> +Tools that turn commits into email, for example, use the first paragraph\n>  on the Subject: line and the rest of the commit in the body.\n\nThis is a good change, as the previous sentence says the norm for\nthe first paragraph is a single line.\n\n> diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt\n> index 7e83288..499c26a 100644\n> --- a/Documentation/git-for-each-ref.txt\n> +++ b/Documentation/git-for-each-ref.txt\n> @@ -100,7 +100,7 @@ Fields that have name-email-date tuple as its value (`author`,\n>  `committer`, and `tagger`) can be suffixed with `name`, `email`,\n>  and `date` to extract the named component.\n>  \n> -The first line of the message in a commit and tag object is\n> +The first paragraph of the message in a commit and tag object is\n>  `subject`, the remaining lines are `body`.  The whole message\n>  is `contents`.\n\nThis may need a bit more explanation.  Just saying \"First Paragraph\"\nwithout saying that for all commits in a sane project it is the same\nas \"First Line\" will make the reader wonder \"What happens to the\nsecond and subsequent lines?\" (the answer is that the first paragraph \nis made into a single looooooong line).\n\n> diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt\n> index 9674f9d..e6f6d0e 100644\n> --- a/Documentation/git-format-patch.txt\n> +++ b/Documentation/git-format-patch.txt\n> @@ -57,10 +57,12 @@ output, unless the `--stdout` option is specified.\n>  If `-o` is specified, output files are created in <dir>.  Otherwise\n>  they are created in the current working directory.\n>  \n> -By default, the subject of a single patch is \"[PATCH] First Line\" and\n> +By default, the subject of a single patch is \"[PATCH] First Paragraph\" and\n>  the subject when multiple patches are output is \"[PATCH n/m] First\n> +Paragraph\". Note that \"First Paragraph\" consists of text in the commit message\n> +prior to the first completely blank line (see the DISCUSSION section\n> +in linkgit:git-commit[1]).  To force 1/1 to be added for a single patch,\n> +use `-n`.  To omit patch numbers from the subject, use `-N`.\n\nDitto.\n\n> diff --git a/Documentation/git-shortlog.txt b/Documentation/git-shortlog.txt\n> index dfd4d0c..9464932 100644\n> --- a/Documentation/git-shortlog.txt\n> +++ b/Documentation/git-shortlog.txt\n> @@ -15,7 +15,7 @@ DESCRIPTION\n>  -----------\n>  Summarizes 'git log' output in a format suitable for inclusion\n>  in release announcements. Each commit will be grouped by author and\n> -the first line of the commit message will be shown.\n> +the first paragraph of the commit message will be shown.\n\nDitto.\n\n> diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt\n> index f7815e9..92f97e6 100644\n> --- a/Documentation/gitcore-tutorial.txt\n> +++ b/Documentation/gitcore-tutorial.txt\n> @@ -956,7 +956,7 @@ $ git show-branch --topo-order --more=1 master mybranch\n>  ------------------------------------------------\n>  \n>  The first two lines indicate that it is showing the two branches\n> -and the first line of the commit log message from their\n> +and the first paragraph of the commit log message from their\n>  top-of-the-tree commits, you are currently on `master` branch\n>  (notice the asterisk `\\*` character), and the first column for\n>  the later output lines is used to show commits contained in the\n\nDitto.\n\n> diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt\n> index 1c16066..a1bc56c 100644\n> --- a/Documentation/gittutorial.txt\n> +++ b/Documentation/gittutorial.txt\n> @@ -139,7 +139,7 @@ A note on commit messages: Though not required, it's a good idea to\n>  begin the commit message with a single short (less than 50 character)\n>  line summarizing the change, followed by a blank line and then a more\n>  thorough description.  Tools that turn commits into email, for\n> -example, use the first line on the Subject: line and the rest of the\n> +example, use the first paragraph on the Subject: line and the rest of the\n>  commit in the body.\n\nThis is a good change, as it is clear that you are expected to write\na single line in the first paragraph in the previous sentence.\n\n> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\n> index fe6fb72..dd2f985 100644\n> --- a/Documentation/user-manual.txt\n> +++ b/Documentation/user-manual.txt\n> @@ -1126,7 +1126,7 @@ Though not required, it's a good idea to begin the commit message\n>  with a single short (less than 50 character) line summarizing the\n>  change, followed by a blank line and then a more thorough\n>  description.  Tools that turn commits into email, for example, use\n> -the first line on the Subject line and the rest of the commit in the\n> +the first paragraph on the Subject line and the rest of the commit in the\n>  body.\n\nDitto.\n"},{"id":"198955","messageId":"AAA3E50085B245A18F97A80EB059F11D@PhilipOakley","threadId":"31521","inReplyTo":"5051D4A0.4060608@codeweavers.com","subject":"Re: [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2012-09-13T18:45:50Z","receivedAt":"2012-09-13T18:45:50Z","isPatch":true,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Jeremy White\" <jwhite@codeweavers.com>\nSent: Thursday, September 13, 2012 1:42 PM\n> The discussion of email subject throughout the documentation is\n> misleading; it indicates that the first line will become the subject.\n> In fact, the first and second and third lines will become the subject,\n> up until the first full blank line.  Describing it as the first \n> paragraph\n\nThis  \"up until the first full blank line\" part should also be in the \ndocumentation itself to clarify how a 'paragraph' is delineated. I've \nshown one place it could go below.\n\n> is more accurate.\n>\n> Signed-off-by: Jeremy White <jwhite@codeweavers.com>\n> ---\n> Documentation/git-commit.txt       |    2 +-\n> Documentation/git-for-each-ref.txt |    2 +-\n> Documentation/git-format-patch.txt |    8 +++++---\n> Documentation/git-shortlog.txt     |    2 +-\n> Documentation/gitcore-tutorial.txt |    2 +-\n> Documentation/gittutorial.txt      |    2 +-\n> Documentation/user-manual.txt      |    2 +-\n> 7 files changed, 11 insertions(+), 9 deletions(-)\n>\n> diff --git a/Documentation/git-commit.txt \n> b/Documentation/git-commit.txt\n> index e99bb14..a61bca9 100644\n> --- a/Documentation/git-commit.txt\n> +++ b/Documentation/git-commit.txt\n> @@ -349,7 +349,7 @@ DISCUSSION\n> Though not required, it's a good idea to begin the commit message\n> with a single short (less than 50 character) line summarizing the\n> change, followed by a blank line and then a more thorough description.\n> -Tools that turn commits into email, for example, use the first line\n> +Tools that turn commits into email, for example, use the first \n> paragraph\n> on the Subject: line\n\n    \"up until the first full blank line\"\n\n>                               and the rest of the commit in the body.\n>\n> include::i18n.txt[]\n> diff --git a/Documentation/git-for-each-ref.txt \n> b/Documentation/git-for-each-ref.txt\n> index 7e83288..499c26a 100644\n> --- a/Documentation/git-for-each-ref.txt\n> +++ b/Documentation/git-for-each-ref.txt\n> @@ -100,7 +100,7 @@ Fields that have name-email-date tuple as its \n> value (`author`,\n> `committer`, and `tagger`) can be suffixed with `name`, `email`,\n> and `date` to extract the named component.\n>\n> -The first line of the message in a commit and tag object is\n> +The first paragraph of the message in a commit and tag object is\n> `subject`, the remaining lines are `body`.  The whole message\n> is `contents`.\n>\n> diff --git a/Documentation/git-format-patch.txt \n> b/Documentation/git-format-patch.txt\n> index 9674f9d..e6f6d0e 100644\n> --- a/Documentation/git-format-patch.txt\n> +++ b/Documentation/git-format-patch.txt\n> @@ -57,10 +57,12 @@ output, unless the `--stdout` option is specified.\n> If `-o` is specified, output files are created in <dir>.  Otherwise\n> they are created in the current working directory.\n>\n> -By default, the subject of a single patch is \"[PATCH] First Line\" and\n> +By default, the subject of a single patch is \"[PATCH] First \n> Paragraph\" and\n> the subject when multiple patches are output is \"[PATCH n/m] First\n> -Line\". To force 1/1 to be added for a single patch, use `-n`.  To \n> omit\n> -patch numbers from the subject, use `-N`.\n> +Paragraph\". Note that \"First Paragraph\" consists of text in the \n> commit message\n> +prior to the first completely blank line (see the DISCUSSION section\n> +in linkgit:git-commit[1]).  To force 1/1 to be added for a single \n> patch,\n> +use `-n`.  To omit patch numbers from the subject, use `-N`.\n>\n> If given `--thread`, `git-format-patch` will generate `In-Reply-To` \n> and\n> `References` headers to make the second and subsequent patch mails \n> appear\n> diff --git a/Documentation/git-shortlog.txt \n> b/Documentation/git-shortlog.txt\n> index dfd4d0c..9464932 100644\n> --- a/Documentation/git-shortlog.txt\n> +++ b/Documentation/git-shortlog.txt\n> @@ -15,7 +15,7 @@ DESCRIPTION\n> -----------\n> Summarizes 'git log' output in a format suitable for inclusion\n> in release announcements. Each commit will be grouped by author and\n> -the first line of the commit message will be shown.\n> +the first paragraph of the commit message will be shown.\n>\n> Additionally, \"[PATCH]\" will be stripped from the commit description.\n>\n> diff --git a/Documentation/gitcore-tutorial.txt \n> b/Documentation/gitcore-tutorial.txt\n> index f7815e9..92f97e6 100644\n> --- a/Documentation/gitcore-tutorial.txt\n> +++ b/Documentation/gitcore-tutorial.txt\n> @@ -956,7 +956,7 @@ $ git show-branch --topo-order --more=1 master \n> mybranch\n> ------------------------------------------------\n>\n> The first two lines indicate that it is showing the two branches\n> -and the first line of the commit log message from their\n> +and the first paragraph of the commit log message from their\n> top-of-the-tree commits, you are currently on `master` branch\n> (notice the asterisk `\\*` character), and the first column for\n> the later output lines is used to show commits contained in the\n> diff --git a/Documentation/gittutorial.txt \n> b/Documentation/gittutorial.txt\n> index 1c16066..a1bc56c 100644\n> --- a/Documentation/gittutorial.txt\n> +++ b/Documentation/gittutorial.txt\n> @@ -139,7 +139,7 @@ A note on commit messages: Though not required, \n> it's a good idea to\n> begin the commit message with a single short (less than 50 character)\n> line summarizing the change, followed by a blank line and then a more\n> thorough description.  Tools that turn commits into email, for\n> -example, use the first line on the Subject: line and the rest of the\n> +example, use the first paragraph on the Subject: line and the rest of \n> the\n> commit in the body.\n>\n> Git tracks content not files\n> diff --git a/Documentation/user-manual.txt \n> b/Documentation/user-manual.txt\n> index fe6fb72..dd2f985 100644\n> --- a/Documentation/user-manual.txt\n> +++ b/Documentation/user-manual.txt\n> @@ -1126,7 +1126,7 @@ Though not required, it's a good idea to begin \n> the commit message\n> with a single short (less than 50 character) line summarizing the\n> change, followed by a blank line and then a more thorough\n> description.  Tools that turn commits into email, for example, use\n> -the first line on the Subject line and the rest of the commit in the\n> +the first paragraph on the Subject line and the rest of the commit in \n> the\n> body.\n>\n> [[ignoring-files]]\n> -- \n> 1.7.9.5\n>\n>\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n>\n> -----\n> No virus found in this message.\n> Checked by AVG - www.avg.com\n> Version: 2012.0.2221 / Virus Database: 2437/5266 - Release Date: \n> 09/13/12\n> \n"},{"id":"198964","messageId":"505248C3.7000803@codeweavers.com","threadId":"31521","inReplyTo":"7vehm593v8.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","fromName":"Jeremy White","fromEmail":"jwhite@codeweavers.com","sentAt":"2012-09-13T20:57:39Z","receivedAt":"2012-09-13T20:57:39Z","isPatch":true,"sender":{"key":"jwhite@codeweavers.com","avatar":"https://avatars.githubusercontent.com/u/1063742?v=4"},"body":"Thanks for the feedback; new patch inbound.  Minor nits:\n\n>> diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt\n>> index f7815e9..92f97e6 100644\n>> --- a/Documentation/gitcore-tutorial.txt\n>> +++ b/Documentation/gitcore-tutorial.txt\n>> @@ -956,7 +956,7 @@ $ git show-branch --topo-order --more=1 master mybranch\n>>  ------------------------------------------------\n>>  \n>>  The first two lines indicate that it is showing the two branches\n>> -and the first line of the commit log message from their\n>> +and the first paragraph of the commit log message from their\n>>  top-of-the-tree commits, you are currently on `master` branch\n>>  (notice the asterisk `\\*` character), and the first column for\n>>  the later output lines is used to show commits contained in the\n> \n> Ditto.\n\nI did not substantially alter this. The emphasis of this section\nis on the broader show-branch output, and belaboring the subject would\nbe distracting and unnecessary imho.\n\nCheers,\n\nJeremy\n"},{"id":"198969","messageId":"7vwqzx62vv.fsf@alter.siamese.dyndns.org","threadId":"31521","inReplyTo":"505248C3.7000803@codeweavers.com","subject":"Re: [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-09-13T21:15:16Z","receivedAt":"2012-09-13T21:15:16Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeremy White <jwhite@codeweavers.com> writes:\n\n> Thanks for the feedback; new patch inbound.  Minor nits:\n>\n>>> diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt\n>>> index f7815e9..92f97e6 100644\n>>> --- a/Documentation/gitcore-tutorial.txt\n>>> +++ b/Documentation/gitcore-tutorial.txt\n>>> @@ -956,7 +956,7 @@ $ git show-branch --topo-order --more=1 master mybranch\n>>>  ------------------------------------------------\n>>>  \n>>>  The first two lines indicate that it is showing the two branches\n>>> -and the first line of the commit log message from their\n>>> +and the first paragraph of the commit log message from their\n>>>  top-of-the-tree commits, you are currently on `master` branch\n>>>  (notice the asterisk `\\*` character), and the first column for\n>>>  the later output lines is used to show commits contained in the\n>> \n>> Ditto.\n>\n> I did not substantially alter this. The emphasis of this section\n> is on the broader show-branch output, and belaboring the subject would\n> be distracting and unnecessary imho.\n\nYeah, but if that is the focus of this part of the documentation,\nwouldn't a patch to update \"the first line\" with something more\ngeneric like \"title of the commit\" be more appropriate?\n"},{"id":"198971","messageId":"50524E23.2040507@codeweavers.com","threadId":"31521","inReplyTo":"7vwqzx62vv.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","fromName":"Jeremy White","fromEmail":"jwhite@codeweavers.com","sentAt":"2012-09-13T21:20:35Z","receivedAt":"2012-09-13T21:20:35Z","isPatch":true,"sender":{"key":"jwhite@codeweavers.com","avatar":"https://avatars.githubusercontent.com/u/1063742?v=4"},"body":">> I did not substantially alter this. The emphasis of this section\n>> is on the broader show-branch output, and belaboring the subject would\n>> be distracting and unnecessary imho.\n> \n> Yeah, but if that is the focus of this part of the documentation,\n> wouldn't a patch to update \"the first line\" with something more\n> generic like \"title of the commit\" be more appropriate?\n\nSee my patch; I went with 'first part'.  That, I think, does not\nmislead (the goal of my change), but also does not distract from\nthe main point of the section (detailing the various bits of\ngit show-branch).\n\nCheers,\n\nJeremy\n"},{"id":"198976","messageId":"7vmx0t625z.fsf@alter.siamese.dyndns.org","threadId":"31521","inReplyTo":"50524E23.2040507@codeweavers.com","subject":"Re: [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-09-13T21:30:48Z","receivedAt":"2012-09-13T21:30:48Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeremy White <jwhite@codeweavers.com> writes:\n\n>>> I did not substantially alter this. The emphasis of this section\n>>> is on the broader show-branch output, and belaboring the subject would\n>>> be distracting and unnecessary imho.\n>> \n>> Yeah, but if that is the focus of this part of the documentation,\n>> wouldn't a patch to update \"the first line\" with something more\n>> generic like \"title of the commit\" be more appropriate?\n>\n> See my patch; I went with 'first part'.  That, I think, does not\n> mislead (the goal of my change), but also does not distract from\n> the main point of the section (detailing the various bits of\n> git show-branch).\n\nFor that kind of casual wording, we have used \"title\" on this list\nfor quite a long time, I think.  So I'd rather see a change that\njust says \"title\" (if we are making such a change to the\ndocumentation, that is).  This is not a very strong preference,\nthough.\n"},{"id":"198980","messageId":"50525D51.7000504@codeweavers.com","threadId":"31521","inReplyTo":"7vmx0t625z.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.","fromName":"Jeremy White","fromEmail":"jwhite@codeweavers.com","sentAt":"2012-09-13T22:25:21Z","receivedAt":"2012-09-13T22:25:21Z","isPatch":true,"sender":{"key":"jwhite@codeweavers.com","avatar":"https://avatars.githubusercontent.com/u/1063742?v=4"},"body":"> For that kind of casual wording, we have used \"title\" on this list\n> for quite a long time, I think.  So I'd rather see a change that\n> just says \"title\" (if we are making such a change to the\n> documentation, that is).  This is not a very strong preference,\n> though.\n\nAh, I was unaware of the use of title, and I rather like it.\n\nv3 inbound making more use of title, and hopefully addressing\nyour other points as well.\n\nCheers,\n\nJeremy\n"}]}