Hi, On Mar 16, 2012, at 7:13 AM, Henrik Ingo wrote:
> It used to say things like:
> "merge lp:~brianaker/drizzle/fix-libdrizzle-version"
> -> I can see that libdrizzle version was bumped as discussed on
> mailing list / Skype. This is a good commit message.
>
> Now it says just:
> "Merge staging tree to trunk."
> -> Every commit message is identical. Zero information value.
We need a way to strip the message that the original patch used and place it
into the commit.
> It seems you are actually attacking the right problem, because the
> last message is:
> "Merging bzr://localhost/drizzle/show to Build branch"
That is my bad, what I did was merge from a fixed local branch (instead of one
up on lp). I will make a point of not doing that in the future.
> This is an improvement, but if the branch name could really point to
> the lp:~user/drizzle/branchname as before, it would be even
> friendlier.
>
> The information value in the commit message is what I was after the
> whole time, just that my initial guess for a reason was wrong.
One issue is that we have to do a merge, not pull, from other folks tree to
push into trunk. So,... how do we have bzr extract that data from "bzr status
--verbose"
Cheers,
-Brian
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
