Re: A couple of things we need with the git conversion

From: Murray S. Kucherawy <msk_at_blackops.org>
Date: Fri, 29 Oct 2010 18:55:11 -0700 (PDT)

On Sat, 30 Oct 2010, Daniel Black wrote:
>> 2) I'd like to get commit emails going again.
>
> I was looking through this last night. didn't get around to an email but
> it seems you found the sf doco too.
>
> Could set hooks.emailprefix= on the server to remove the [SCM] prefix.

I don't mind the [SCM], so I'll leave it unless someone has a specific
preference.

> 3) project methodology
>
> While most of what currently practiced is portable to git it seems according
> to these references that the current trunk (or master in git speak) should be
> the pristine working release and there should be a different branch for the
> intergration of branches (develop in the first ref and next in the second).
>
> http://nvie.com/posts/a-successful-git-branching-model/
> http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
>
> Once we get this convention in place I'll get the hydra build farm using
> this branch for build testing.

I don't mind that change but wouldn't it be better to tell hydra to use a
staging branch rather than the master, which is presumably
already-released code?

> 4) cleanup
>
> Can we delete the closed branch? Seems like recommended practice. For
> new/current branches merging with a --no-ff will create an approprate
> version history.

Did you mean all closed branches, or did you mean a specific one?
Received on Sat Oct 30 2010 - 01:55:37 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:32:54 PST