From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Joe Perches <joe@perches.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jeff Garzik <jgarzik@pobox.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH - net-2.6.24 0/2] Introduce and use print_ip and print_ipv6
Date: Thu, 20 Sep 2007 20:46:31 +0300 (EEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709202044090.7669@kivilampi-30.cs.helsinki.fi> (raw)
In-Reply-To: <1190301928.26101.102.camel@localhost>
On Thu, 20 Sep 2007, Joe Perches wrote:
> On Thu, 2007-09-20 at 07:55 -0700, Randy Dunlap wrote:
> > How large are the patches if you posted them for review instead
> > of just referencing gits for them? (which cuts down on review
> > possibilities)
>
> The v4 is ~130kb, the v6 ~35kb.
>
> There is a gitweb available at:
>
> print_ip:
> http://repo.or.cz/w/linux-2.6/trivial-mods.git?a=shortlog;h=print_ipv4
> commit diff:
> http://repo.or.cz/w/linux-2.6/trivial-mods.git?a=commitdiff;h=1e3a30d5d8b49b3accca07cc84ecf6d977cacdd5
>
> print_ipv6:
> http://repo.or.cz/w/linux-2.6/trivial-mods.git?a=shortlog;h=print_ipv6
> commit diff:
> http://repo.or.cz/w/linux-2.6/trivial-mods.git?a=commitdiff;h=e96b794a57a164db84379e2baf5fe2622a5ae3bf
...Alternatively you could split it up a bit and send those smaller
chunks for reviewing purposes only (even though it would be combined
to a single big patch in the end).
--
i.
next prev parent reply other threads:[~2007-09-20 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 6:53 [PATCH - net-2.6.24 0/2] Introduce and use print_ip and print_ipv6 Joe Perches
2007-09-20 14:55 ` Randy Dunlap
2007-09-20 15:25 ` Joe Perches
2007-09-20 17:46 ` Ilpo Järvinen [this message]
2007-09-20 23:05 ` Thomas Graf
2007-09-20 23:20 ` Joe Perches
2007-09-26 2:29 ` David Miller
2007-09-26 4:36 ` Joe Perches
2007-09-26 5:11 ` David Miller
2007-09-26 5:18 ` Jeff Garzik
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=Pine.LNX.4.64.0709202044090.7669@kivilampi-30.cs.helsinki.fi \
--to=ilpo.jarvinen@helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.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
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;
as well as URLs for NNTP newsgroup(s).