On Fri, Oct 23, 2015 at 11:04:59AM +0200, Peter Zijlstra wrote:
> > If you think this is actually the wrong thing, is it worth trying
> > to fix the git docs to deprecate this option?
>
> As said in the other email; git has different standards than lkml. By
> now we're just one of many many users of git.
Even git developers will create a new thread for a large (more than
2-3 patches) patch set. However, for a single patch, people have
chained the -v3 version of the draft --- not to the v2 version,
though, but to the review of the patch. And I've seen that behavior
on some LKML lists, and I'm certainly fine with it on linux-ext4.
But if you have a huge patch series, and you keep chaining it unto the
8th, 10th, 22nd version, it certainly will get **very** annoying for
some MUA's.
The bottom line is that you should use common sense, and it can be
hard to document every last bit of what should be "common sense" into
a rule that is followed by robots or a perl script. (Which is one of
the reasons why I'm not fond of the philosophy that every single last
checkpatch warning or error should result in a "cleanup" patch, but
that's another issue.)
Cheers,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
