From: Al Viro <viro@ftp.linux.org.uk>
To: Joe Perches <joe@perches.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: convert #include "linux/..." to #include <linux/...> [PATCH]s follow
Date: Sun, 19 Aug 2007 22:58:35 +0000 [thread overview]
Message-ID: <20070819225835.GW21089@ftp.linux.org.uk> (raw)
In-Reply-To: <1187563756.4200.167.camel@localhost>
On Sun, Aug 19, 2007 at 03:49:16PM -0700, Joe Perches wrote:
> On Sun, 2007-08-19 at 23:44 +0100, Al Viro wrote:
> > Except that some instances are legitimate (e.g. there was a bunch in
> > arch/um, IIRC)...
>
> I guess it's a good thing that vger seems to have rejected
> that 140KB patch I sent against arch/um and include/asm-um.
It would be a better thing if you
* did builds of the patched trees (allmodconfig for uml/i386 and
uml/amd64 in this case)
* figured out that one can send a reference to branch in git tree
(with summary/shortlog/diffstat) using somewhat less than 140KB...
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ftp.linux.org.uk>
To: Joe Perches <joe@perches.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: convert #include "linux/..." to #include <linux/...> [PATCH]s follow
Date: Sun, 19 Aug 2007 23:58:35 +0100 [thread overview]
Message-ID: <20070819225835.GW21089@ftp.linux.org.uk> (raw)
In-Reply-To: <1187563756.4200.167.camel@localhost>
On Sun, Aug 19, 2007 at 03:49:16PM -0700, Joe Perches wrote:
> On Sun, 2007-08-19 at 23:44 +0100, Al Viro wrote:
> > Except that some instances are legitimate (e.g. there was a bunch in
> > arch/um, IIRC)...
>
> I guess it's a good thing that vger seems to have rejected
> that 140KB patch I sent against arch/um and include/asm-um.
It would be a better thing if you
* did builds of the patched trees (allmodconfig for uml/i386 and
uml/amd64 in this case)
* figured out that one can send a reference to branch in git tree
(with summary/shortlog/diffstat) using somewhat less than 140KB...
next prev parent reply other threads:[~2007-08-19 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 22:17 convert #include "linux/..." to #include <linux/...> [PATCH]s Joe Perches
2007-08-19 22:17 ` convert #include "linux/..." to #include <linux/...> [PATCH]s follow Joe Perches
2007-08-19 22:19 ` Jesper Juhl
2007-08-19 22:19 ` Jesper Juhl
2007-08-19 22:33 ` convert #include "linux/..." to #include <linux/...> [PATCH]s Jan Engelhardt
2007-08-19 22:33 ` convert #include "linux/..." to #include <linux/...> [PATCH]s follow Jan Engelhardt
2007-08-19 22:44 ` Al Viro
2007-08-19 22:44 ` Al Viro
2007-08-19 22:49 ` convert #include "linux/..." to #include <linux/...> [PATCH]s Joe Perches
2007-08-19 22:49 ` convert #include "linux/..." to #include <linux/...> [PATCH]s follow Joe Perches
2007-08-19 22:58 ` Al Viro [this message]
2007-08-19 22:58 ` Al Viro
2007-08-19 23:05 ` convert #include "linux/..." to #include <linux/...> [PATCH]s Joe Perches
2007-08-19 23:05 ` convert #include "linux/..." to #include <linux/...> [PATCH]s follow Joe Perches
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=20070819225835.GW21089@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=apw@shadowen.org \
--cc=jengelh@computergmbh.de \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.