Re: [PATCHv5 0/4] Push options

From: Jeff King <peff@peff.net>
Date: Jul 14, 2016, 18:50 UTC
Message-ID: <20160714185037.GG16497@sigill.intra.peff.net>
In-Reply-To: <CAGZ79kaj2vfvS3RXCWqkZNdF7UkjAuv_J00kENPjz7SNTUV7BQ@mail.gmail.com>

On Thu, Jul 14, 2016 at 11:48:58AM -0700, Stefan Beller wrote:

Show 14 quoted lines

> > 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