ufl team mailing list archive
-
ufl team
-
Mailing list archive
-
Message #01877
Re: [noreply@xxxxxxxxxxxxx: [Branch ~ufl-core/ufl/main] Rev 1051: erge]
-
To:
ufl@xxxxxxxxxxxxxxxxxxx
-
From:
"Garth N. Wells" <gnw20@xxxxxxxxx>
-
Date:
Thu, 12 May 2011 09:37:24 +0100
-
In-reply-to:
<20110512082836.GE1808@smaug>
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10
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