Neal Kreitzinger wrote: > "prerelease freeze" is not in the git-workflows manpage. I'm interested in > how you-all do this because I use the git-workflows mangpage to help me > figure out my workflows. Can someone explain? See http://en.wikipedia.org/wiki/Freeze_(software_engineering) In git's incarnation of it, presumably the idea is that new features do not get merged to 'master' (while they still would be merged to 'pu' and perhaps 'next'). See also <http://sites.google.com/site/maintnotes/> for some direct discussion of the branches used by git.git. Hope that helps, Jonathan [1] [1] Unrelated note: please try to preserve the cc list in replies (i.e., "reply-to-all-by-mail" rather than "followup"). -- 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