Andreas Ericsson wrote: > Junio C Hamano wrote: >> >> In addition, you can keep older maintenance track around, i.e. >> >> git branch maint-X.Y.(Z-1) maint >> git checkout maint >> git merge master >> >> so that maintenance releases for even older codebase _could_ be issued >> _if_ necessary. >> > > Assuming one tags ones releases (which one should, and git.git does), > creating maint-X.Y.Z when it's actually needed is a far better approach. This is only correct if the current tip of the maint branch is in fact the last tagged release i.e. that there is nothing pending on the maint branch that is intended for a maintenance release on the older codebase. Cheers, Raman -- 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
