{"thread":{"id":"27798","subject":"Naming Conventions for Branches","startedAt":"2011-07-12T18:24:45Z","lastAt":"2011-07-12T18:24:45Z","messageCount":1,"participants":["thaddeus"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"171172","messageId":"1310495085285-6576242.post@n2.nabble.com","threadId":"27798","inReplyTo":null,"subject":"Naming Conventions for Branches","fromName":"thaddeus","fromEmail":"t-tcambron@trxtraining.com","sentAt":"2011-07-12T18:24:45Z","receivedAt":"2011-07-12T18:24:45Z","isPatch":false,"sender":{"key":"t-tcambron@trxtraining.com","avatar":null},"body":"Is it common to have a different name for each branch, descriptive of the\nproject is contains or is it more common to have one dedicated name (for\ninstance QA2) for the branch on which projects change based on need. \nBest\n\n--\nView this message in context: http://git.661346.n2.nabble.com/Naming-Conventions-for-Branches-tp6576242p6576242.html\nSent from the git mailing list archive at Nabble.com.\n"}]}