{"thread":{"id":"23028","subject":"FEATURE REQUEST: Comment assignment on branches","startedAt":"2010-03-15T08:33:29Z","lastAt":"2010-03-16T14:36:43Z","messageCount":13,"participants":["Maxim Treskin","René Scharfe","Junio C Hamano","Nicolas Sebrecht","Mark Lodato","Miles Bader","Sverre Rabbelier","Matthieu Moy","Nguyen Thai Ngoc Duy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"136867","messageId":"be8f531d1003150133n3ea64109u7d573dbd533ffa48@mail.gmail.com","threadId":"23028","inReplyTo":null,"subject":"FEATURE REQUEST: Comment assignment on branches","fromName":"Maxim Treskin","fromEmail":"zerthurd@gmail.com","sentAt":"2010-03-15T08:33:29Z","receivedAt":"2010-03-15T08:33:29Z","isPatch":false,"sender":{"key":"zerthurd@gmail.com","avatar":null},"body":"Hello\n\nIs it possible to add comments assignment to branches?\nSomething like:\n\n$ git branch --comment=\"New branch with implementation of some features\" br14\n\n$ git branch\n br14\n* master\n\n$ git branch --comments\n br14 (New branch with implementation of some features)\n* master\n\nand when configuration variable branch.comments == true, this behavior\nis default.\n\nThank you\n\n-- \nMaxim Treskin\n"},{"id":"136874","messageId":"4B9EA22E.1010103@lsrfire.ath.cx","threadId":"23028","inReplyTo":"be8f531d1003150133n3ea64109u7d573dbd533ffa48@mail.gmail.com","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"René Scharfe","fromEmail":"rene.scharfe@lsrfire.ath.cx","sentAt":"2010-03-15T21:10:06Z","receivedAt":"2010-03-15T21:10:06Z","isPatch":false,"sender":{"key":"l.s.r@web.de","avatar":"https://avatars.githubusercontent.com/u/26122331?v=4"},"body":"Am 15.03.2010 09:33, schrieb Maxim Treskin:\n> Hello\n> \n> Is it possible to add comments assignment to branches?\n> Something like:\n> \n> $ git branch --comment=\"New branch with implementation of some features\" br14\n> \n> $ git branch\n> br14\n> * master\n> \n> $ git branch --comments\n> br14 (New branch with implementation of some features)\n> * master\n> \n> and when configuration variable branch.comments == true, this behavior\n> is default.\n\nHmm. You could name your branch\n\"br14/new-branch-with-implementation-of-some-features\" instead of\n\"br14\". With command line completion you would only have to hit two\nextra keys (slash tab) and could enjoy a meaningful branch name everywhere.\n\nRené\n"},{"id":"136877","messageId":"7v3a01jmp9.fsf@alter.siamese.dyndns.org","threadId":"23028","inReplyTo":"4B9EA22E.1010103@lsrfire.ath.cx","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-03-15T21:32:02Z","receivedAt":"2010-03-15T21:32:02Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"René Scharfe writes:\n\n> Am 15.03.2010 09:33, schrieb Maxim Treskin:\n>> Hello\n>> \n>> Is it possible to add comments assignment to branches?\n>> Something like:\n>> \n>> $ git branch --comment=\"New branch with implementation of some features\" br14\n>> \n>> $ git branch\n>> br14\n>> * master\n>> \n>> $ git branch --comments\n>> br14 (New branch with implementation of some features)\n>> * master\n>> \n>> and when configuration variable branch.comments == true, this behavior\n>> is default.\n>\n> Hmm. You could name your branch\n> \"br14/new-branch-with-implementation-of-some-features\" instead of\n> \"br14\". With command line completion you would only have to hit two\n> extra keys (slash tab) and could enjoy a meaningful branch name everywhere.\n\nAnother thing to worry about is how \"--comments\" and \"-v\" would interact\nwith each other.\n"},{"id":"136878","messageId":"20100315213221.GA12941@vidovic","threadId":"23028","inReplyTo":"be8f531d1003150133n3ea64109u7d573dbd533ffa48@mail.gmail.com","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Nicolas Sebrecht","fromEmail":"nicolas.s.dev@gmx.fr","sentAt":"2010-03-15T21:32:21Z","receivedAt":"2010-03-15T21:32:21Z","isPatch":false,"sender":{"key":"nicolas.s.dev@gmx.fr","avatar":null},"body":"The 15/03/10, Maxim Treskin wrote:\n\n> Is it possible to add comments assignment to branches?\n> Something like:\n\nAren't you looking for 'git notes'?\n\n-- \nNicolas Sebrecht\n"},{"id":"136879","messageId":"7vhbohi80n.fsf@alter.siamese.dyndns.org","threadId":"23028","inReplyTo":"20100315213221.GA12941@vidovic","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-03-15T21:34:32Z","receivedAt":"2010-03-15T21:34:32Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nicolas Sebrecht writes:\n\n> The 15/03/10, Maxim Treskin wrote:\n>\n>> Is it possible to add comments assignment to branches?\n>> Something like:\n>\n> Aren't you looking for 'git notes'?\n\nI don't think so. Notes are fundamentally per-commit.\n\nMy understanding is that it is more like:\n\n [branch \"frotz\"]\n \tcomment = \"This is to add frotz command to the system\"\n\nI do not have a fundamental objection to such a feature, but the\npresentation needs to be well thought out.\n"},{"id":"136905","messageId":"ca433831003151735u697c5e3fm431dd98bcf48f7bf@mail.gmail.com","threadId":"23028","inReplyTo":"7v3a01jmp9.fsf@alter.siamese.dyndns.org","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Mark Lodato","fromEmail":"lodatom@gmail.com","sentAt":"2010-03-16T00:35:03Z","receivedAt":"2010-03-16T00:35:03Z","isPatch":false,"sender":{"key":"lodatom@gmail.com","avatar":"https://avatars.githubusercontent.com/u/58860?v=4"},"body":"On Mon, Mar 15, 2010 at 5:32 PM, Junio C Hamano wrote:\n>\n> Another thing to worry about is how \"--comments\" and \"-v\" would interact\n> with each other.\n\nWhat about putting the comment on the line below, with the same level\nof indentation?\n\n maint 8fcaca3 don't use default revision if a rev was specified\n (preparation for the next maintenance release)\n* master c24138b Merge branch 'sd/format-patch-to'\n (preparation for the next feature release)\n next 0ae494e Merge branch 'pb/log-first-parent-p-m' into next\n (semi-stable test branch for integration into master)\n"},{"id":"136913","messageId":"7vk4tdxcgt.fsf@alter.siamese.dyndns.org","threadId":"23028","inReplyTo":"ca433831003151735u697c5e3fm431dd98bcf48f7bf@mail.gmail.com","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-03-16T01:49:22Z","receivedAt":"2010-03-16T01:49:22Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Mark Lodato writes:\n\n> On Mon, Mar 15, 2010 at 5:32 PM, Junio C Hamano wrote:\n>>\n>> Another thing to worry about is how \"--comments\" and \"-v\" would interact\n>> with each other.\n>\n> What about putting the comment on the line below, with the same level\n> of indentation?\n\nThat, or in an order that is the other way around.\n\nI think eventually people realize that \"branch -v\" and \"tag -l -n $n\" are\nsimilar and start making noises about \"branch -v -n $n\" to internally run\n\"log --oneline\". To prepare for such a feature creep, comment first then\ncommit would probably be a better idea, but I dunno.\n"},{"id":"136920","messageId":"buovdcw6fjj.fsf@dhlpc061.dev.necel.com","threadId":"23028","inReplyTo":"7vhbohi80n.fsf@alter.siamese.dyndns.org","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Miles Bader","fromEmail":"miles@gnu.org","sentAt":"2010-03-16T04:45:04Z","receivedAt":"2010-03-16T04:45:04Z","isPatch":false,"sender":{"key":"miles@gnu.org","avatar":"https://gravatar.com/avatar/01069b69593af7bff28e2f97afeb3644ae6fe2f5f56cb3a8cf34c5fb8c36efe5?d=mp&s=160"},"body":"Junio C Hamano writes:\n> My understanding is that it is more like:\n>\n> [branch \"frotz\"]\n> \tcomment = \"This is to add frotz command to the system\"\n>\n> I do not have a fundamental objection to such a feature, but the\n> presentation needs to be well thought out.\n\nThis would seem especially useful for publicly visible branches...\n\n-Miles\n\n-- \nAbsurdity, n. A statement or belief manifestly inconsistent with one's own\nopinion.\n"},{"id":"136941","messageId":"7vljdsu7kc.fsf@alter.siamese.dyndns.org","threadId":"23028","inReplyTo":"buovdcw6fjj.fsf@dhlpc061.dev.necel.com","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-03-16T06:03:31Z","receivedAt":"2010-03-16T06:03:31Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Miles Bader writes:\n\n> Junio C Hamano writes:\n>> My understanding is that it is more like:\n>>\n>> [branch \"frotz\"]\n>> \tcomment = \"This is to add frotz command to the system\"\n>>\n>> I do not have a fundamental objection to such a feature, but the\n>> presentation needs to be well thought out.\n>\n> This would seem especially useful for publicly visible branches...\n\nIf you mean by \"publicly visible\" branches in public repositories, I\nsuspect not. At places like repo.or.cz, github, or installations managed\nby gitosis, you typically do not have direct access to $GIT_DIR/config\nfiles (they belong to site administrators) in your repositories, and that\nis not likely to change for security reasons.\n"},{"id":"136943","messageId":"fc339e4a1003152320i12a7d4b2p711f6b5d0eda9bcd@mail.gmail.com","threadId":"23028","inReplyTo":"7vljdsu7kc.fsf@alter.siamese.dyndns.org","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Miles Bader","fromEmail":"miles@gnu.org","sentAt":"2010-03-16T06:20:54Z","receivedAt":"2010-03-16T06:20:54Z","isPatch":false,"sender":{"key":"miles@gnu.org","avatar":"https://gravatar.com/avatar/01069b69593af7bff28e2f97afeb3644ae6fe2f5f56cb3a8cf34c5fb8c36efe5?d=mp&s=160"},"body":"On Tue, Mar 16, 2010 at 3:03 PM, Junio C Hamano wrote:\n>> This would seem especially useful for publicly visible branches...\n>\n> If you mean by \"publicly visible\" branches in public repositories, I\n> suspect not.  At places like repo.or.cz, github, or installations managed\n> by gitosis, you typically do not have direct access to $GIT_DIR/config\n> files (they belong to site administrators) in your repositories, and that\n> is not likely to change for security reasons.\n\nHm, ok you're right... which is a shame... :(\n\n'cause a \"pushable branch description\" would be ace!\n\n[I take it git has no \"limited remote metadata change\" function...?]\n\n-Miles\n\n-- \nDo not taunt Happy Fun Ball.\n"},{"id":"136944","messageId":"fabb9a1e1003152326m4d67f48bkc207ba7368cb54e4@mail.gmail.com","threadId":"23028","inReplyTo":"fc339e4a1003152320i12a7d4b2p711f6b5d0eda9bcd@mail.gmail.com","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-03-16T06:26:26Z","receivedAt":"2010-03-16T06:26:26Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Tue, Mar 16, 2010 at 07:20, Miles Bader wrote:\n> On Tue, Mar 16, 2010 at 3:03 PM, Junio C Hamano wrote:\n>> If you mean by \"publicly visible\" branches in public repositories, I\n>> suspect not.  At places like repo.or.cz, github, or installations managed\n>> by gitosis, you typically do not have direct access to $GIT_DIR/config\n>> files (they belong to site administrators) in your repositories, and that\n>> is not likely to change for security reasons.\n>\n> Hm, ok you're right... which is a shame... :(\n\nWhich is also why I think it would be nice if we could teach notes to\nannotate branches/tags/the whole shaboodle. I really think that a\ngeneric way to annotate something under /refs/ would be useful.\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"136955","messageId":"vpq4okgd8kp.fsf@bauges.imag.fr","threadId":"23028","inReplyTo":"fabb9a1e1003152326m4d67f48bkc207ba7368cb54e4@mail.gmail.com","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2010-03-16T07:33:42Z","receivedAt":"2010-03-16T07:33:42Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Sverre Rabbelier writes:\n\n> Which is also why I think it would be nice if we could teach notes to\n> annotate branches/tags/the whole shaboodle. I really think that a\n> generic way to annotate something under /refs/ would be useful.\n\nmeetoo.\n\nToday, we have .git/description which is used by gitweb (and others?)\nto say what the repository contains. That would be nice to have the\nsame thing for branches. Take\nhttp://git.kernel.org/?p=git/git.git;a=summary for example: commits\nhave a comment, tag have a comment, and branches just say:\n\n10 hours ago \tman \tshortlog | log | tree\n10 hours ago \thtml \tshortlog | log | tree\n22 hours ago \tpu \tshortlog | log | tree\n22 hours ago \tnext \tshortlog | log | tree\n23 hours ago \tmaster \tshortlog | log | tree\n2 days ago \tmaint \tshortlog | log | tree\n5 days ago \ttodo \tshortlog | log | tree\n\nA newbie will have a hard time understanding what \"pu\" means, while a\none-liner saying (proposed update, may be rewound at any time) would\ngive most of the required information. Actually, ideally, this could\nbe a message like commit message (i.e. one-liner, blank line, and\nbody).\n\n(My 2 cents)\n\n--\nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"136959","messageId":"fcaeb9bf1003160736w7749f358p6ee8f86e6c3a32c6@mail.gmail.com","threadId":"23028","inReplyTo":"4B9EA22E.1010103@lsrfire.ath.cx","subject":"Re: FEATURE REQUEST: Comment assignment on branches","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2010-03-16T14:36:43Z","receivedAt":"2010-03-16T14:36:43Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On 3/16/10, René Scharfe wrote:\n> Am 15.03.2010 09:33, schrieb Maxim Treskin:\n>\n> > Hello\n> >\n> > Is it possible to add comments assignment to branches?\n> > Something like:\n> >\n> > $ git branch --comment=\"New branch with implementation of some features\" br14\n> >\n> > $ git branch\n> > br14\n> > * master\n> >\n> > $ git branch --comments\n> > br14 (New branch with implementation of some features)\n> > * master\n> >\n> > and when configuration variable branch.comments == true, this behavior\n> > is default.\n>\n>\n> Hmm. You could name your branch\n> \"br14/new-branch-with-implementation-of-some-features\" instead of\n> \"br14\". With command line completion you would only have to hit two\n> extra keys (slash tab) and could enjoy a meaningful branch name everywhere.\n\nIf only completion works across shells. Another idea: put notes in a\nblob, tagged with \"notes/branchname\" or another convention.\n\nThen if you want to see description of branch \"br14\", do \"git show\nnotes/br14\". Teaching \"git branch\" to show it is easy.\n-- \nDuy\n"}]}