On Sun, Mar 25, 2018 at 08:46:53PM +0000, Ævar Arnfjörð Bjarmason wrote: > There were some side discussions at Git Merge this year about how we > should just update the README to tell users they can dig these up from > the history if the need them, do that. > > Looking at the "git log" for this directory we get quite a bit more > patch churn than we should here, mainly from things fixing various > tree-wide issues. > > There's also confusion on the list occasionally about how these should > be treated, "Re: [PATCH 1/4] stash: convert apply to > builtin" (<CA+CzEk9QpmHK_TSBwQfEedNqrcVSBp3xY7bdv1YA_KxePiFeXw@xxxxxxxxxxxxxx>) > being the latest example of that. I'm in favor of this. I don't think I've ever come across this directory and _not_ been annoyed (because it was the result of a grep and was just cluttering the results). And I think your README change leaves a nice signpost for people who might be digging around for plumbing examples. > The people on CC got this, but it seems the git ML rejected the message > as it's too big. The abbreviated patches is here quoted inline, and at: > https://github.com/avar/git/commit/cc578c81c2cb2999b1a0b73954610bd74951c37b I was going to suggest re-sending with "-D", but it looks like "git apply" will not apply such a patch (even though it could in theory realize that the current blob matches the preimage sha1 and it would be safe to remove it). -Peff
