From: Larry McVoy <lm@bitmover.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHES] today's batch of "nuking kernel/ksyms.c"
Date: Wed, 1 Oct 2003 21:02:06 -0700 [thread overview]
Message-ID: <20031002040206.GA2382@work.bitmover.com> (raw)
In-Reply-To: <20031002030338.GB1699@conectiva.com.br>
If this is all the same idea why are you putting it in multiple changesets?
Where I work we have a rule "one idea, one changeset", which makes it far
easier to track down problems later.
On Thu, Oct 02, 2003 at 12:03:38AM -0300, Arnaldo Carvalho de Melo wrote:
> ChangeSet@1.1396, 2003-10-02 02:39:04-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/fcntl.c
> ChangeSet@1.1395, 2003-10-02 02:32:40-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/attr.c
> ChangeSet@1.1394, 2003-10-02 02:28:31-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/filesystems.c
> ChangeSet@1.1393, 2003-10-02 02:14:22-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/fs-writeback.c
> ChangeSet@1.1392, 2003-10-02 02:10:28-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/partitions/check.c
> ChangeSet@1.1391, 2003-10-02 02:02:17-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/select.c
> ChangeSet@1.1390, 2003-10-02 01:54:54-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/locks.c
> ChangeSet@1.1389, 2003-10-02 01:46:05-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/namespace.c
> ChangeSet@1.1388, 2003-10-02 01:31:38-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/file_table.c
> ChangeSet@1.1387, 2003-10-02 01:26:03-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/open.c
> ChangeSet@1.1386, 2003-10-02 01:17:47-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/stat.c
> ChangeSet@1.1385, 2003-10-02 01:04:15-03:00, acme@parisc.kerneljanitors.org
> o kernel/ksyms.c: move relevant EXPORT_SYMBOLs to fs/read_write.c
next prev parent reply other threads:[~2003-10-02 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 3:03 [PATCHES] today's batch of "nuking kernel/ksyms.c" Arnaldo Carvalho de Melo
2003-10-02 4:02 ` Larry McVoy [this message]
2003-10-02 9:44 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly 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=20031002040206.GA2382@work.bitmover.com \
--to=lm@bitmover.com \
--cc=acme@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox