Re: log format for vc-bzr

[Óscar Fuentes]

Andreas Schwab <address@hidden> writes:

> Óscar Fuentes <address@hidden> writes:
>
>> With the distributed development style that encourages committing often,
>> the history that comes from the merged branch can be very boring and
>> irrelevant. Something like this:
>>
>> 15.23 gone lunch
>> 15.24 some refactoring
>> 15.25 seems ready for testing
>
> These are completely useless commit messages that should never occur
> in a sane history.

Useless for whom? For the developer who is working on the feature? No,
they are small milestones and state-savers (for synchronizing his
desktop with his laptop, for instance). For the other developers? Yes,
but that's the reason why merged history is hidden by default.

Of course those example commits are intentionally chosen for making a
point. But the idea is: while you work on your personal branch, you
commit as you please; when you merge your changes, use a nice commit
message.

And finally, with a distributed workflow like the advocated on the wiki,
if you show the merged history on the log you will see a lot of
redundancy like this:

3324 Fixed bug #242
3324.1 Fixed bug #242

-- 
Óscar