{"thread":{"id":"29402","subject":"More support on branch description?","startedAt":"2012-01-19T14:14:55Z","lastAt":"2012-01-20T08:24:18Z","messageCount":5,"participants":["Nguyen Thai Ngoc Duy","Michael Schubert","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"182787","messageId":"CACsJy8D0_EB6jN7KxpzLtnPnj0HjdU6sNHJRyqXJf-2-ZNatFA@mail.gmail.com","threadId":"29402","inReplyTo":null,"subject":"More support on branch description?","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2012-01-19T14:14:55Z","receivedAt":"2012-01-19T14:14:55Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"Hi,\n\nThe coming v1.7.9 will introduce branch description, mainly used in\nintegration process. I think we could make it useful for users who\ndon't extensively use request-pull/format-patch. Showing a short\nsummary along with branch name in \"git branch\" would be nice. \"branch\n-v\" is already used for something else, maybe we can come up with\nanother option, or \"-v -v\"? Another place we could show branch\ndescription is \"git status\". What do you think?\n-- \nDuy\n"},{"id":"182789","messageId":"4F183365.5010607@elegosoft.com","threadId":"29402","inReplyTo":"CACsJy8D0_EB6jN7KxpzLtnPnj0HjdU6sNHJRyqXJf-2-ZNatFA@mail.gmail.com","subject":"Re: More support on branch description?","fromName":"Michael Schubert","fromEmail":"mschub@elegosoft.com","sentAt":"2012-01-19T15:14:45Z","receivedAt":"2012-01-19T15:14:45Z","isPatch":false,"sender":{"key":"mschub@elegosoft.com","avatar":null},"body":"On 01/19/2012 03:14 PM, Nguyen Thai Ngoc Duy wrote:\n> The coming v1.7.9 will introduce branch description, mainly used in\n> integration process. I think we could make it useful for users who\n> don't extensively use request-pull/format-patch. Showing a short\n> summary along with branch name in \"git branch\" would be nice. \"branch\n> -v\" is already used for something else, maybe we can come up with\n> another option, or \"-v -v\"? Another place we could show branch\n> description is \"git status\". What do you think?\n\nJunio suggested a new option \"--verbose-format\" for branch some weeks\nago:\n\n\thttp://thread.gmane.org/gmane.comp.version-control.git/186727\n\nI planned on working on it, but haven't found the time yet nor do I\nreally know which way to go.? (pretty.c seems to be the right\nplace for format code, but it's very commit format specific atm.)\n"},{"id":"182791","messageId":"CACsJy8DTw-8Sm09hzHoHP8eFVGCX_kkrvhj+8v3MXz2eohfaEQ@mail.gmail.com","threadId":"29402","inReplyTo":"4F183365.5010607@elegosoft.com","subject":"Re: More support on branch description?","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2012-01-19T15:24:24Z","receivedAt":"2012-01-19T15:24:24Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Thu, Jan 19, 2012 at 10:14 PM, Michael Schubert wrote:\n> Junio suggested a new option \"--verbose-format\" for branch some weeks\n> ago:\n>\n>        http://thread.gmane.org/gmane.comp.version-control.git/186727\n>\n> I planned on working on it, but haven't found the time yet nor do I\n> really know which way to go.? (pretty.c seems to be the right\n> place for format code, but it's very commit format specific atm.)\n\nThanks. I must have missed that. There's another piece of formatting\ncode in \"for-each-ref --format\" command (I happened to have a look at\nit a few days ago). It's ref-specific, probably closer than pretty.c\nfor this kind of stuff.\n-- \nDuy\n"},{"id":"182818","messageId":"7v4nvrib7u.fsf@alter.siamese.dyndns.org","threadId":"29402","inReplyTo":"CACsJy8D0_EB6jN7KxpzLtnPnj0HjdU6sNHJRyqXJf-2-ZNatFA@mail.gmail.com","subject":"Re: More support on branch description?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-01-19T22:22:45Z","receivedAt":"2012-01-19T22:22:45Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nguyen Thai Ngoc Duy writes:\n\n> The coming v1.7.9 will introduce branch description, mainly used in\n> integration process. I think we could make it useful for users who\n> don't extensively use request-pull/format-patch. Showing a short\n> summary along with branch name in \"git branch\" would be nice.\n\nI agree that it would be nice to give users access to the information even\nif the branch ends up being merged to the master branch by you and never\nleaves your repository by itself.\n\nYou however are misguided to say \"Showing a short summary along...\".\n\nThe branch description support is to give users a place to record detailed\nexplanation about a branch, similar in size to what you would normally\nplace in a log message of a commit or a cover letter of a series. There\nwasn't any convenient place to do so for a branch that is (1) inherently a\nmoving target while it is being developed and (2) is not a good match for\ntags and notes.\n\nThere already is a good place for a brief summary and it is called \"branch\nname\". Name your branches just like you name your functions.\n"},{"id":"182845","messageId":"CACsJy8CULRFOk0-LqL03gHD2jy39rb39MCdMnQ5r2bnTyDjBKw@mail.gmail.com","threadId":"29402","inReplyTo":"7v4nvrib7u.fsf@alter.siamese.dyndns.org","subject":"Re: More support on branch description?","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2012-01-20T08:24:18Z","receivedAt":"2012-01-20T08:24:18Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Fri, Jan 20, 2012 at 5:22 AM, Junio C Hamano wrote:\n> You however are misguided to say \"Showing a short summary along...\".\n\nIt should have been \"short status\".\n\n> The branch description support is to give users a place to record detailed\n> explanation about a branch, similar in size to what you would normally\n> place in a log message of a commit or a cover letter of a series.  There\n> wasn't any convenient place to do so for a branch that is (1) inherently a\n> moving target while it is being developed and (2) is not a good match for\n> tags and notes.\n\nI was thinking about that (and wondering if I abused\nbranch.*.description), maybe we can have a similar convention for\ncommit message, one short line, empty line, then more detail\nexplanation. But branch.*.description is tied to\nformat-patch/request-pull, maybe another config key.\n\n> There already is a good place for a brief summary and it is called \"branch\n> name\". Name your branches just like you name your functions.\n\nYes, but it's not suitable for current status of the branch.\n-- \nDuy\n"}]}