Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1702362
| From | Linus Torvalds <torvalds@linux-foundation.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V2] get_maintainer: Prepare for separate MAINTAINERS files |
| Date | 2017-08-02 20:20 +0200 |
| Message-ID | <ua6pr-51S-9@gated-at.bofh.it> (permalink) |
| References | <u6vPr-3JJ-5@gated-at.bofh.it> <u9WT9-7j8-39@gated-at.bofh.it> <ua6fM-4Ya-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Aug 2, 2017 at 11:06 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> IMO, the parse-maintainters.pl (sorting) script makes the need for separate
> MAINTAINERS files much less important since the file can be "fixed" easily
> at any time.
For me it's not the "fixing". It's the inevitable merge mess, and the
two hundred commits that I have to go through.
That said, the extra time just to look for MAINTAINERS files makes me
unhappy. It may be just .3s on Joe's machine, but it's presumably much
more when things aren't in the filesystem caches. I (like apparently
Joe) have an SSD so it's not a big deal for me, but..
Just having a single MAINTAINERS directory would alleviate that concern.
Linus
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH V2] get_maintainer: Prepare for separate MAINTAINERS files Joe Perches <joe@perches.com> - 2017-08-02 10:10 +0200
Re: [PATCH V2] get_maintainer: Prepare for separate MAINTAINERS files Randy Dunlap <rdunlap@infradead.org> - 2017-08-02 20:10 +0200
Re: [PATCH V2] get_maintainer: Prepare for separate MAINTAINERS files Linus Torvalds <torvalds@linux-foundation.org> - 2017-08-02 20:20 +0200
Re: [PATCH V2] get_maintainer: Prepare for separate MAINTAINERS files Joe Perches <joe@perches.com> - 2017-08-02 22:40 +0200
csiph-web