On Sun, Oct 28, 2012 at 5:49 PM, Philip Oakley <philipoakley@xxxxxxx> wrote: > If I read it right it was where two users can tag two different commits with > the same tag name [e.g. 'Release_V3.3'] and the last person to push wins, so > anyone in the team can change what is to be the released version! Philip, Please look at Kacper's patch and Angelo's response to it. He seems to be asking that tags not be permitted to be pushed as if doing so were a "fast-forward" update. This weekend I was, in part, trying to figure out what the correct CC list for that patch would be, what the documentation change would be, what changes would need to be made to the advice, what test would need to be included, and so on to build a proper patch bundle. All of that while tring to keep the house from "falling in" (I've been doing some cleaning) and prepare for the Northeastern USA Coast to be doused and blasted by Sandy in about a day and a half. If we decide to continue in the path that Kacper and I have stumbled upon (with Angelo's prodding) I'd appreciate a little help putting all of this together to mesh with the aforementioned patch. (Heck, if there's somebody better than me to take this over I'd be game for that too...) -- -Drew Northup -------------------------------------------------------------- "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59 -- 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