{"thread":{"id":"36515","subject":"RE: Recording the current branch on each commit?","startedAt":"2014-04-28T06:42:06Z","lastAt":"2014-04-28T06:42:06Z","messageCount":1,"participants":["Max Kirillov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"239835","messageId":"20140427234205.96eec638b311907e2368f42b42021fd8.e03a1e7076.wbe@email02.secureserver.net","threadId":"36515","inReplyTo":null,"subject":"RE: Recording the current branch on each commit?","fromName":"Max Kirillov","fromEmail":"max@max630.net","sentAt":"2014-04-28T06:42:06Z","receivedAt":"2014-04-28T06:42:06Z","isPatch":false,"sender":{"key":"max@max630.net","avatar":"https://avatars.githubusercontent.com/u/381560?v=4"},"body":"> Personally, I am _strongly_ opposed.  How I name and juggle my private\n> branches is nobody else's business in a distributed version control\n> system.\n> \n> They are private.  My personal workflow.  Not part of a commit.\n\nMercurial inherits the branch label from previous commit, unless\nit's specified by user, I think this could be quite reasonable behavior.\n(if make them at all, I don't think this specific branch label feature\nshould be implemented in git core, but rather there should be a way\nto extend git so that it makes them)\n\n-- \nMax\n"}]}