On Friday, August 1, 2014, Dennis Kaarsemaker <dennis@xxxxxxxxxxxxxxx> wrote: > > On di, 2014-07-29 at 17:40 -0500, Nico Williams wrote: > > (or all of a repo's branches) > > > > Teamware recorded whether it had any "children" and warned about > > rebasing published contents. Perhaps git could do the same. > > Git doesn't record this directly, but you can see which known remote > branches contain the tip of a branch: Yes, but that says nothing about whether they accept non-ff merge pushes, or should reject them, and it says nothing about whether they are intended to be seen as "published" in the sense of having stable history. (Teamware would mark repos as published when cloned, but that often meant needing to reset that flag [it wasn't a flag, but i'm eliding irrelevant details].) Yes, non-fast-forward pushes can be rejected with a hook, but a flag that could be set with a git command would be more convenient. -- 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