ufl team mailing list archive

[Martin Sandve Alnæs <martinal@xxxxxxxxx>]

On 12 May 2011 10:37, Garth N. Wells <gnw20@xxxxxxxxx> wrote:
>
>
> On 12/05/11 09:28, Anders Logg wrote:
>> I've been trying the new foo, foo/trunk, foo/work setup and it's
>> working pretty well, except for the missing commit messages.
>>
>> I write a commit message when I commit in work, but when I merge it
>> into trunk, I just enter 'merge' since I don't want to repeat the
>> commit message I've already written. When a large piece of work is
>> merged in (consisting of many changesets), it's natural to write a
>> summary when it's merged in, but if it's just a single changeset, I
>> don't want to repeat the message I just wrote.
>>
>> Any suggestions for how to handle this?
>>
>
> Work the way we did before? I don't see the problem with the old
> approach. It worked, was simple, and we never lost history.

No history is lost either way, the problem is that when history is
rewritten (renumbered), we loose unique revision numbers.

Martin

>
> Garth
>
>> --
>> Anders
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~ufl
>> Post to     : ufl@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ufl
>> More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ufl
> Post to     : ufl@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ufl
> More help   : https://help.launchpad.net/ListHelp
>