From: Dan Williams <email@example.com> To: Jason Gunthorpe <firstname.lastname@example.org> Cc: Dan Carpenter <email@example.com>, Jonathan Corbet <firstname.lastname@example.org>, Jens Axboe <email@example.com>, Dave Jiang <firstname.lastname@example.org>, ksummit <email@example.com>, linux-nvdimm <firstname.lastname@example.org>, Vishal Verma <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, email@example.com Subject: Re: [Ksummit-discuss] [PATCH v2 3/3] libnvdimm, MAINTAINERS: Maintainer Entry Profile Date: Tue, 17 Sep 2019 14:59:11 -0700 Message-ID: <CAPcyv4jR9ufeXyXOwnnPBC2kbHNfamZu93s4hM371=j-sACAjA@mail.gmail.com> (raw) In-Reply-To: <20190917161608.GA12866@ziepe.ca> On Tue, Sep 17, 2019 at 9:16 AM Jason Gunthorpe <firstname.lastname@example.org> wrote: > > On Fri, Sep 13, 2019 at 02:48:50PM +0300, Dan Carpenter wrote: > > > It used to be that infiniband used "sizeof foo" instead of sizeof(foo) > > but now there is a new maintainer. > > These days I run everything through checkpatch and generally don't > want to see much deviation from the 'normal' style, a few minor > clang-format quibbles and other check patch positives excluded. > > This means when people touch lines they have to adjust minor things > like the odd 'sizeof foo' to make it conforming. > > Like others there is a big historical mismatch and the best I hope for > is that new stuff follow the cannonical style. Trying to guess what > some appropriate mongral style is for each patch is just a waste of my > time. > > I also hold drivers/infiniband as an example of why the column > alignment style is harmful. That has not aged well and is the cause of > a lot of ugly things. > > > There is one subsystem where the maintainer is super strict rules that > > you can't use "I" or "we" in the commit message. So you can't say "I > > noticed a bug while reviewing", you have to say "The code has a bug". > > Ah, the imperative mood nitpick. This one is very exciting to explain > to non-native speakers. With many regular submitters I'm still at the > "I wish you would use proper grammer and sentence structure" phase.. > > These days I just end up copy editing most of the commit messages :( > > > I don't think it's shaming, I think it's validating. Everyone just > > insists that since it's written in the Book of Rules then it's our fault > > for not reading it. It's like those EULA things where there is more > > text than anyone can physically read in a life time. > > Yeah, I tend to agree. > > The big special cases with high patch volumes (net being the classic > example) should remain special. > > But everyone else is not special, and shouldn't act the same. > > The work people like DanC do with static analysis is valuable, and we > should not be insisting that those contributors have to jump through a > thousand special hoops. > > I have simply viewed it as the job of the maintainer to run the > process and deal with minor nit picks on the fly. > > Maybe that is what we should be documenting? In theory, yes, in practice, as long as there is an exception to the rule, it comes down to a question of "is this case special like net or not?". I'd rather not waste time debating that on a per-subsystem basis vs just getting it all documented for contributors. I do think it is worth clarifying in the guidelines of writing a profile to make an effort to not be special, and that odd looking rules will be questioned (like libnvdimm statement continuation), but lets not fight the new standards fight until it becomes apparent where the outliers lie.
next prev parent reply index Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com> [not found] ` <firstname.lastname@example.org> 2019-09-11 18:43 ` Dan Carpenter 2019-09-11 22:11 ` Jens Axboe 2019-09-12 7:41 ` Dan Williams 2019-09-12 8:24 ` Miguel Ojeda 2019-09-12 10:18 ` Joe Perches 2019-09-12 14:42 ` Miguel Ojeda 2019-09-13 7:09 ` Jonathan Corbet 2019-09-13 11:48 ` Dan Carpenter 2019-09-13 12:18 ` Dan Williams 2019-09-13 15:00 ` Randy Dunlap 2019-09-13 15:46 ` Rob Herring 2019-09-13 16:42 ` Joe Perches 2019-09-13 19:32 ` Rob Herring 2019-09-13 17:57 ` Geert Uytterhoeven 2019-09-16 12:42 ` Jani Nikula 2019-09-17 16:16 ` Jason Gunthorpe 2019-09-17 21:59 ` Dan Williams [this message] 2019-09-13 21:44 ` Martin K. Petersen 2019-09-16 7:01 ` Dan Carpenter 2019-09-16 17:08 ` Martin K. Petersen 2019-09-16 17:15 ` Mark Brown 2019-09-13 2:11 ` Aneesh Kumar K.V 2019-09-13 5:00 ` Greg KH
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAPcyv4jR9ufeXyXOwnnPBC2kbHNfamZu93s4hM371=j-sACAjA@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
BPF Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/bpf/0 bpf/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 bpf bpf/ https://lore.kernel.org/bpf \ firstname.lastname@example.org public-inbox-index bpf Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.bpf AGPL code for this site: git clone https://public-inbox.org/public-inbox.git