On Thu, Jul 14, 2016 at 11:48:58AM -0700, Stefan Beller wrote: > > Hmm. So that is a downside for people who have implemented separate > > DoS protection only in that upgrading git will open a new "hole" > > that they need to plug. But that is their problem, not upstream > > git's. > > > > -Peff > > But this is not specific to DoS protection, but like most features. > Just look at the vendors using linux that think carrying patches out > of tree for their special snowflake hardware is cheaper than getting > it upstream.... (This is not to be read as a snarky comment, but > rather as a pointer to the similarity of the mechanisms involved). > Although I cannot tell offhand another feature that would easily break > downstream customization.
Right. I was serious when I said "their problem, not git's". Most features are a little better off in that they are not a possible negative for somebody downstream to receive them. But again, I don't think that needs to restrict what git releases. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
