How we use Git, part 2

[Gervase Markham]

On 26/11/14 00:04, Randall S. Becker wrote:
> On: 25/11/15 09:30 Gervase Markham wrote:
>> On 25/11/14 14:22, David Lawrence wrote:
>>> Sounds fine to me. I would even go a little further and name it 
>>> bug-218917-gerv or feature-218917-gerv. For people who want to 
>>> contribute that do not have checkin rights, there is always
>>> github as well and they can use similar naming there.
>> When would you choose "bug" and when "feature"? How is expressing
>> that distinction in the branch name useful? Or do you just think it
>> reads better?
> 
> I prefer task_218917_gerv, to be perfectly frank. 

My question is, why have a prefix at all? If it's always the same, it
just makes branch names unnecessarily longer. If it's different, what is
the process for choosing the different prefixes?

> For most commits, I
> put in the Bugzilla URL anyway (Mylyn does it automagically), so
> looking up the details of the bug or feature is really not far. 

I still think there is value in being able to execute "git branch", and
see a list of current branches and which bugs they relate to.

> I do
> not really like a purely numeric prefix, as this can be a little
> confusing between branches and abbreviated git versions if you are
> looking at change trees. 

OK, there's some merit in that. But why not just go with "b" (for "bug")
as the prefix to solve that problem?

Gerv