Chris Patti <cpatti@xxxxxxxxx> writes: >> git branch -D next-release >> git branch next-release release-3.15 >> >> (I personally think branches are nicer for this since tags are "supposed" to >> be immutable.) > > Won't either of those things create a 'next-release' that's frozen in > time where the release-3.15 branch is *right now*? I suspect that most people go about this the other way around. You keep the next-release branch that goes forward, and your automated process would follow that one. When you really cut a release, you tag the tip of next-release, i.e. "git tag v3.15 next-release", to give it a name. -- 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