On Thursday, April 14, 2011 15:31:13 Chris Patti wrote: > On Thu, Apr 14, 2011 at 5:24 PM, Wesley J. Landaker <wjl@xxxxxxxxxxxxx> wrote: > > Why not just use a tag or a branch ? > > Won't either of those things create a 'next-release' that's frozen in > time where the release-3.15 branch is *right now*? > > This is for a CI system (Bamboo) so we need next-release to act as if > we were using release-3.15 itself. Yes, you are right, but I was thinking about how I usually see it done and do it in my projects is that "next-release" is what you always are working on, and "release-3.15" would only be made when 3.15 is finalized. It sounds like you are doing it the other way around, in which case I agree that being able to easily share symbolic-refs would be solve the problem -- but I don't know how to do that, other than, say, a hook script that everyone uses. Maybe someone else will chime in with a better solution? =) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html