{"thread":{"id":"8527","subject":"Attributes for commits","startedAt":"2007-06-09T13:11:48Z","lastAt":"2007-06-10T02:10:53Z","messageCount":4,"participants":["Paul Franz","Johan Herland","Robin Rosenberg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"44445","messageId":"466AA714.4050500@comcast.net","threadId":"8527","inReplyTo":null,"subject":"Attributes for commits","fromName":"Paul Franz","fromEmail":"thefranz@comcast.net","sentAt":"2007-06-09T13:11:48Z","receivedAt":"2007-06-09T13:11:48Z","isPatch":false,"sender":{"key":"thefranz@comcast.net","avatar":null},"body":" I am a ClearCase administrator and one of the things that I love \nabout it is the ability to assign attributes to versions of files. Is \nthere anybody thinking of adding the ability to assign attributes to a \ncommit? I ask because I was thinking about how I would move from \nClearCase to git and part of our process is to assign the BugNum \nattribute to every checkin so that we can see what bugs have been fixed. \nWe also track the files checked in the bug tracking software to. Thus \ngiving us a two way linkage between repository and the bug tracking \nsystem. This is VERY useful. And I was wondering if there are any \nthought to this for commits.\n\nNow, I will be honest it is possible that this has already been done (I \nhave not read all the documentation yet) and I am justing wasting \nbandwidth. In which, please excuse my ignorance and tell me to just RTFM.\n\nPaul Franz\n\n-- \n\n-------------------------------------------\n\nThere are seven sins in the world.\n Wealth without work.\n Pleasure without conscience.\n Knowledge without character.\n Commerce without morality.\n Science without humanity.\n Worship without sacrifice.\n Politics without principle.\n\n -- Mohandas Gandhi\n\n-------------------------------------------\n"},{"id":"44446","messageId":"200706091549.39383.johan@herland.net","threadId":"8527","inReplyTo":"466AA714.4050500@comcast.net","subject":"Re: Attributes for commits","fromName":"Johan Herland","fromEmail":"johan@herland.net","sentAt":"2007-06-09T13:49:39Z","receivedAt":"2007-06-09T13:49:39Z","isPatch":false,"sender":{"key":"johan@herland.net","avatar":"https://avatars.githubusercontent.com/u/547031?v=4"},"body":"On Saturday 09 June 2007, Paul Franz wrote:\n> I am a ClearCase administrator and one of the things that I love \n> about it is the ability to assign attributes to versions of files. Is \n> there anybody thinking of adding the ability to assign attributes to a \n> commit? I ask because I was thinking about how I would move from \n> ClearCase to git and part of our process is to assign the BugNum \n> attribute to every checkin so that we can see what bugs have been fixed. \n> We also track the files checked in the bug tracking software to. Thus \n> giving us a two way linkage between repository and the bug tracking \n> system. This is VERY useful. And I was wondering if there are any \n> thought to this for commits.\n> \n> Now, I will be honest it is possible that this has already been done (I \n> have not read all the documentation yet) and I am justing wasting \n> bandwidth. In which, please excuse my ignorance and tell me to just RTFM.\n\nWell, we're sort of in the process of getting there. I posted an initial\nproof-of-concept implementation of git 'notes' a while back. Git notes is\na general mechanism for providing free-form annotations on git objects\nafter they've been created. My initial posting sparked a discussion [1],\nand I'm currently in the process of reimplementing the notes concept\nbased on the outcome of that discussion.\n\nSo the thing you want will hopefully be in a future release.\n\n\nHave fun!\n\n...Johan\n\n[1]: http://thread.gmane.org/gmane.comp.version-control.git/46770/focus=48540\n\n-- \nJohan Herland, \nwww.herland.net\n"},{"id":"44482","messageId":"200706092048.52142.robin.rosenberg.lists@dewire.com","threadId":"8527","inReplyTo":"466AA714.4050500@comcast.net","subject":"Re: Attributes for commits","fromName":"Robin Rosenberg","fromEmail":"robin.rosenberg.lists@dewire.com","sentAt":"2007-06-09T18:48:51Z","receivedAt":"2007-06-09T18:48:51Z","isPatch":false,"sender":{"key":"robin.rosenberg@dewire.com","avatar":"https://avatars.githubusercontent.com/u/46357?v=4"},"body":"lördag 09 juni 2007 skrev Paul Franz:\n> I am a ClearCase administrator and one of the things that I love \n> about it is the ability to assign attributes to versions of files. Is \n> there anybody thinking of adding the ability to assign attributes to a \n> commit? I ask because I was thinking about how I would move from \n> ClearCase to git and part of our process is to assign the BugNum \n> attribute to every checkin so that we can see what bugs have been fixed. \n> We also track the files checked in the bug tracking software to. Thus \n> giving us a two way linkage between repository and the bug tracking \n> system. This is VERY useful. And I was wondering if there are any \n> thought to this for commits.\n> \n> Now, I will be honest it is possible that this has already been done (I \n> have not read all the documentation yet) and I am justing wasting \n> bandwidth. In which, please excuse my ignorance and tell me to just RTFM.\n> \n> Paul Franz\n> \n\nWe use the convention of putting the bug number as the first work on the first line of\nthe checkin, e.g. \"3399 Add attributes for commits\". The advantage over other methods\nis that it is always there, without the need to further investigations of assigned attributes.\n\nThis convention has nothing to do with Git though. It works with any type of repo.\n\n-- robin\n"},{"id":"44525","messageId":"466B5DAD.9060601@comcast.net","threadId":"8527","inReplyTo":"200706092048.52142.robin.rosenberg.lists@dewire.com","subject":"Re: Attributes for commits","fromName":"Paul Franz","fromEmail":"thefranz@comcast.net","sentAt":"2007-06-10T02:10:53Z","receivedAt":"2007-06-10T02:10:53Z","isPatch":false,"sender":{"key":"thefranz@comcast.net","avatar":null},"body":"But the question is how many allow you to easily query this info. That \nis one of the things I like about ClearCase's use of attributes is the \nability to query the repository about where it is set. For example, in \nthe case of git an attribute called \"Status\" on the commit could help \ncommunicate to others what the status of a commit or better yet an \nattribute on a branch. The one thing that I have realized is that change \nmanagement is all about communication and the repositories are just one \nmore way of communicating especially if the proper information can be \nextracted and maintained by the repository. A good example of this is \nCVS and merges. It is not CVS does merging poorly. It is that:\n\n 1) It has no mechanism in place for itself to know that the merge \nhas been taken place between different branches.\n 2) There is no way for people to know that the changes from one \nbranch has been merged to another.\n\nThe second is where meta data helps. In the case of ClearCase, they \nsomething called a hyper-link that tells that a change to a file has \nbeen merged from one branch to another and ClearCase uses this to know \nhow to merge future changes.\n\nNow, I am not trying to turn git into ClearCase. I just see attributes \nas a great way to help communicate things, from status of a branch to \nwhat bug this change is related. Of course, part of adding attributes \nwould be adding a way to query git to find the commits or branches that \nhave the associated attributes.\n\nPaul Franz\n\nRobin Rosenberg wrote:\n> lördag 09 juni 2007 skrev Paul Franz:\n> \n>> I am a ClearCase administrator and one of the things that I love \n>> about it is the ability to assign attributes to versions of files. Is \n>> there anybody thinking of adding the ability to assign attributes to a \n>> commit? I ask because I was thinking about how I would move from \n>> ClearCase to git and part of our process is to assign the BugNum \n>> attribute to every checkin so that we can see what bugs have been fixed. \n>> We also track the files checked in the bug tracking software to. Thus \n>> giving us a two way linkage between repository and the bug tracking \n>> system. This is VERY useful. And I was wondering if there are any \n>> thought to this for commits.\n>>\n>> Now, I will be honest it is possible that this has already been done (I \n>> have not read all the documentation yet) and I am justing wasting \n>> bandwidth. In which, please excuse my ignorance and tell me to just RTFM.\n>>\n>> Paul Franz\n>>\n>> \n>\n> We use the convention of putting the bug number as the first work on the first line of\n> the checkin, e.g. \"3399 Add attributes for commits\". The advantage over other methods\n> is that it is always there, without the need to further investigations of assigned attributes.\n>\n> This convention has nothing to do with Git though. It works with any type of repo.\n>\n> -- robin\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-- \n\n-------------------------------------------\n\nThere are seven sins in the world.\n Wealth without work.\n Pleasure without conscience.\n Knowledge without character.\n Commerce without morality.\n Science without humanity.\n Worship without sacrifice.\n Politics without principle.\n\n -- Mohandas Gandhi\n\n-------------------------------------------\n"}]}