Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1254516
| From | Theodore Ts'o <tytso@mit.edu> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full |
| Date | 2015-10-23 14:00 +0200 |
| Message-ID | <qmJaO-wP-5@gated-at.bofh.it> (permalink) |
| References | <qdNx0-23T-7@gated-at.bofh.it> <qlM13-6so-9@gated-at.bofh.it> <qm0Qq-33U-23@gated-at.bofh.it> <qmuOu-537-13@gated-at.bofh.it> <qmGwi-5dp-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full Peter Zijlstra <peterz@infradead.org> - 2015-10-21 14:40 +0200
Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full Chris Metcalf <cmetcalf@ezchip.com> - 2015-10-22 22:40 +0200
Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full Frederic Weisbecker <fweisbec@gmail.com> - 2015-10-23 04:40 +0200
Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full Peter Zijlstra <peterz@infradead.org> - 2015-10-23 11:00 +0200
Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full Frederic Weisbecker <fweisbec@gmail.com> - 2015-10-23 15:30 +0200
Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full Peter Zijlstra <peterz@infradead.org> - 2015-10-23 11:10 +0200
Re: [PATCH v8 00/14] support "task_isolation" mode for nohz_full Theodore Ts'o <tytso@mit.edu> - 2015-10-23 14:00 +0200
csiph-web