{"thread":{"id":"24472","subject":"Git Notes on Branches","startedAt":"2010-07-22T20:22:48Z","lastAt":"2010-07-22T21:05:54Z","messageCount":2,"participants":["Joshua Shrader","Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"146018","messageId":"AANLkTinnDBUzoDj-C289l4Kui2qSiKmF-027MzijyCFY@mail.gmail.com","threadId":"24472","inReplyTo":null,"subject":"Git Notes on Branches","fromName":"Joshua Shrader","fromEmail":"jshrader83@gmail.com","sentAt":"2010-07-22T20:22:48Z","receivedAt":"2010-07-22T20:22:48Z","isPatch":false,"sender":{"key":"jshrader83@gmail.com","avatar":null},"body":"I'm wondering if there is a way to (or a reason that would prevent one\nfrom implementing a feature that allows one to) associate a note with\na branch, rather than a specific object.  It seems like a notes object\ncontains a reference to the object that it annotates:\n\nAnnotate 4bd93734af...\n\nRather than forcing this to be a SHA1, can the same approaches as\ntaken with HEAD be employed?  That is, allow it to be either an object\nID, or a local branch?\n\nThis would essentially define a new use case for notes.  Rather than\njust being used to annotate objects, they could be used to describe a\nfeature branch or a bug fix, for example.  Then, when a release is\ncreated (from, say, master), a \"git branches --merged\" will show all\nmerged branches.  Assuming the workflow is to develop on well-defined\nbranches, if each of these branches had a description in an attached\nnote, created Release Notes would be a piece of cake.  Add a\ndescription via \"git notes add feat-branch-2\" that you want to show up\nin the Release Notes once the branch is re-integrated.\n\nI see a potential problem when working remotely and trying to push the\nnote to origin, but I don't think its insurmountable.\n\nThoughts?\n\nJosh\n"},{"id":"146023","messageId":"20100722210554.GA17461@burratino","threadId":"24472","inReplyTo":"AANLkTinnDBUzoDj-C289l4Kui2qSiKmF-027MzijyCFY@mail.gmail.com","subject":"Re: Git Notes on Branches","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2010-07-22T21:05:54Z","receivedAt":"2010-07-22T21:05:54Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi Joshua,\n\nJoshua Shrader wrote:\n\n> I'm wondering if there is a way to (or a reason that would prevent one\n> from implementing a feature that allows one to) associate a note with\n> a branch, rather than a specific object.\n\nExcept for the word “note”, I think your suggestion does not have\nanything to do with git notes at all. :)\n\nSpecial support in gitweb, ‘git branch’, and so on for a branch with\nfiles named after branches and giving descriptions would seem sane\nto me.\n\nHere’s something similar for inspiration:\n\n  http://thread.gmane.org/gmane.comp.version-control.git/33528/focus=33563\n\nGood luck,\nJonathan\n"}]}