{"thread":{"id":"13513","subject":"[PATCH] Rephrased git-describe description","startedAt":"2008-05-14T14:22:27Z","lastAt":"2008-05-14T18:03:02Z","messageCount":4,"participants":["Ian Hilt","Kevin Ballard"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"76941","messageId":"1210774947-27995-1-git-send-email-ian.hilt@gmail.com","threadId":"13513","inReplyTo":null,"subject":"[PATCH] Rephrased git-describe description","fromName":"Ian Hilt","fromEmail":"ian.hilt@gmail.com","sentAt":"2008-05-14T14:22:27Z","receivedAt":"2008-05-14T14:22:27Z","isPatch":true,"sender":{"key":"ian.hilt@gmail.com","avatar":null},"body":"Made description more readable.\n\nSigned-off-by: Ian Hilt \n---\n Documentation/git-describe.txt | 7 ++++---\n 1 files changed, 4 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-describe.txt b/Documentation/git-describe.txt\nindex d9aa2f2..f3f07e4 100644\n--- a/Documentation/git-describe.txt\n+++ b/Documentation/git-describe.txt\n@@ -13,9 +13,10 @@ SYNOPSIS\n DESCRIPTION\n -----------\n The command finds the most recent tag that is reachable from a\n-commit, and if the commit itself is pointed at by the tag, shows\n-the tag. Otherwise, it suffixes the tag name with the number of\n-additional commits and the abbreviated object name of the commit.\n+commit. If the tag points to the commit, then only the tag is\n+shown. Otherwise, the number of additional commits on top of the\n+tagged object and the abbreviated object name of the most recent\n+commit are suffixed to the tag name.\n \n \n OPTIONS\n-- \n1.5.3.7\n"},{"id":"76951","messageId":"19174A63-BE44-4898-9CAD-935BE1A28FFF@sb.org","threadId":"13513","inReplyTo":"1210774947-27995-1-git-send-email-ian.hilt@gmail.com","subject":"Re: [PATCH] Rephrased git-describe description","fromName":"Kevin Ballard","fromEmail":"kevin@sb.org","sentAt":"2008-05-14T16:57:20Z","receivedAt":"2008-05-14T16:57:20Z","isPatch":true,"sender":{"key":"kevin@sb.org","avatar":"https://avatars.githubusercontent.com/u/714?v=4"},"body":"Sorry for the double-posting, Ian, but my first email was rejected \nfrom the list because my mail client attached an HTML part.\n\nOn May 14, 2008, at 9:22 AM, Ian Hilt wrote:\n\n> Made description more readable.\n>\n> Signed-off-by: Ian Hilt \n> ---\n> Documentation/git-describe.txt | 7 ++++---\n> 1 files changed, 4 insertions(+), 3 deletions(-)\n>\n> diff --git a/Documentation/git-describe.txt b/Documentation/git- \n> describe.txt\n> index d9aa2f2..f3f07e4 100644\n> --- a/Documentation/git-describe.txt\n> +++ b/Documentation/git-describe.txt\n> @@ -13,9 +13,10 @@ SYNOPSIS\n> DESCRIPTION\n> -----------\n> The command finds the most recent tag that is reachable from a\n> -commit, and if the commit itself is pointed at by the tag, shows\n> -the tag. Otherwise, it suffixes the tag name with the number of\n> -additional commits and the abbreviated object name of the commit.\n> +commit. If the tag points to the commit, then only the tag is\n> +shown. Otherwise, the number of additional commits on top of the\n> +tagged object and the abbreviated object name of the most recent\n> +commit are suffixed to the tag name.\n\n\nI disagree that this is more readable. Specifically that last \nsentence. In the original description it tells me what it's doing \n(suffixing) before it tells me what objects it's using. In your \nversion, it tells me the objects, then tells me what it's doing \n(suffixing), so I have to effectively process the sentence in reverse. \nIn other words, it took me two readings of your last sentence to match \nthe one reading of the original last sentence.\n\nAlso, you should use a more descriptive commit description. At the \nvery least, do something like\n\ngit-describe: Make description more readable.\n\n-Kevin Ballard\n\n-- \nKevin Ballard\nhttp://kevin.sb.org\nkevin@sb.org\nhttp://www.tildesoft.com\n"},{"id":"76965","messageId":"alpine.LNX.1.10.0805141329020.28504@sys-0.hiltweb.site","threadId":"13513","inReplyTo":"19174A63-BE44-4898-9CAD-935BE1A28FFF@sb.org","subject":"Re: [PATCH] Rephrased git-describe description","fromName":"Ian Hilt","fromEmail":"ian.hilt@gmail.com","sentAt":"2008-05-14T18:00:04Z","receivedAt":"2008-05-14T18:00:04Z","isPatch":true,"sender":{"key":"ian.hilt@gmail.com","avatar":null},"body":"On Wed, 14 May 2008 at 11:57am -0500, Kevin Ballard wrote:\n\n> On May 14, 2008, at 9:22 AM, Ian Hilt wrote:\n>> DESCRIPTION\n>> -----------\n>> The command finds the most recent tag that is reachable from a\n>> -commit, and if the commit itself is pointed at by the tag, shows\n>> -the tag. Otherwise, it suffixes the tag name with the number of\n>> -additional commits and the abbreviated object name of the commit.\n>> +commit. If the tag points to the commit, then only the tag is\n>> +shown. Otherwise, the number of additional commits on top of the\n>> +tagged object and the abbreviated object name of the most recent\n>> +commit are suffixed to the tag name.\n>\n> I disagree that this is more readable. Specifically that last\n> sentence. In the original description it tells me what it's\n> doing (suffixing) before it tells me what objects it's\n> using. In your version, it tells me the objects, then tells me\n> what it's doing (suffixing), so I have to effectively process\n> the sentence in reverse. In other words, it took me two\n> readings of your last sentence to match the one reading of the\n> original last sentence.\n\nHow about this?\n\n The command finds the most recent tag that is reachable from a\n commit. If the tag points to the commit, then only the tag is\n shown. Otherwise, it suffixes to the tag name the number of\n additional commits on top of the tagged object and the\n abbreviated object name of the most recent commit.\n\n> Also, you should use a more descriptive commit description. At the very \n> least, do something like\n>\n> git-describe: Make description more readable.\n\nSomething like this:\n\ngit-describe: Changed subject from commit to tag in the first\n sentence, clarified what the number of commits is\n referring to, and pointed out which object is\n referenced by the suffixed object name.\n\n-- \nIan Hilt\nian.hilt (at) gmail.com\nGnuPG key: 0x4AFC1EE3\n"},{"id":"76966","messageId":"9BD2EC5E-DE16-483B-A6AB-6E4DAF8B3239@sb.org","threadId":"13513","inReplyTo":"alpine.LNX.1.10.0805141329020.28504@sys-0.hiltweb.site","subject":"Re: [PATCH] Rephrased git-describe description","fromName":"Kevin Ballard","fromEmail":"kevin@sb.org","sentAt":"2008-05-14T18:03:02Z","receivedAt":"2008-05-14T18:03:02Z","isPatch":true,"sender":{"key":"kevin@sb.org","avatar":"https://avatars.githubusercontent.com/u/714?v=4"},"body":"On May 14, 2008, at 1:00 PM, Ian Hilt wrote:\n\n> On Wed, 14 May 2008 at 11:57am -0500, Kevin Ballard wrote:\n>\n>> On May 14, 2008, at 9:22 AM, Ian Hilt wrote:\n>>> DESCRIPTION\n>>> -----------\n>>> The command finds the most recent tag that is reachable from a\n>>> -commit, and if the commit itself is pointed at by the tag, shows\n>>> -the tag. Otherwise, it suffixes the tag name with the number of\n>>> -additional commits and the abbreviated object name of the commit.\n>>> +commit. If the tag points to the commit, then only the tag is\n>>> +shown. Otherwise, the number of additional commits on top of the\n>>> +tagged object and the abbreviated object name of the most recent\n>>> +commit are suffixed to the tag name.\n>>\n>> I disagree that this is more readable. Specifically that last\n>> sentence. In the original description it tells me what it's\n>> doing (suffixing) before it tells me what objects it's\n>> using. In your version, it tells me the objects, then tells me\n>> what it's doing (suffixing), so I have to effectively process\n>> the sentence in reverse. In other words, it took me two\n>> readings of your last sentence to match the one reading of the\n>> original last sentence.\n>\n> How about this?\n>\n> The command finds the most recent tag that is reachable from a\n> commit. If the tag points to the commit, then only the tag is\n> shown. Otherwise, it suffixes to the tag name the number of\n> additional commits on top of the tagged object and the\n> abbreviated object name of the most recent commit.\n\nHow about this?\n\nThe command finds the most recent tag that is reachable from a\ncommit. If the tag points to the commit, then only the tag is\nshown. Otherwise, it suffixes the tag name with the number of\nadditional commits on top of the tagged object and the\nabbreviated object name of the most recent commit.\n\n>> Also, you should use a more descriptive commit description. At the \n>> very least, do something like\n>>\n>> git-describe: Make description more readable.\n>\n> Something like this:\n>\n> git-describe: Changed subject from commit to tag in the first\n> sentence, clarified what the number of commits is\n> referring to, and pointed out which object is\n> referenced by the suffixed object name.\n\nSure, you could say that, but I think that just \"git-describe: Make \ndescription more readable\" is enough.\n\n-Kevin Ballard\n\n-- \nKevin Ballard\nhttp://kevin.sb.org\nkevin@sb.org\nhttp://www.tildesoft.com\n"}]}