← Back to team overview

ufl team mailing list archive

Re: [noreply@xxxxxxxxxxxxx: [Branch ~ufl-core/ufl/main] Rev 1051: erge]

 


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.

Garth

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




Follow ups

References