From: David Miller <davem@davemloft.net>
To: harvey.harrison@gmail.com
Cc: joe@perches.com, netdev@vger.kernel.org
Subject: Re: oh crap...
Date: Wed, 29 Oct 2008 11:28:52 -0700 (PDT) [thread overview]
Message-ID: <20081029.112852.153175366.davem@davemloft.net> (raw)
In-Reply-To: <1225301082.5688.24.camel@brick>
From: Harvey Harrison <harvey.harrison@gmail.com>
Date: Wed, 29 Oct 2008 10:24:42 -0700
> %pI6, %pi6
> %pI6 would act just like %p6
> %pi6 would act just like %#p6
I think this form is not a bad idea.
Please send me the patch that does this.
And will you be sending the ipv4 side stuff next?
Thanks.
next prev parent reply other threads:[~2008-10-29 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 8:54 oh crap... (re: %p6) David Miller
2008-10-29 14:55 ` Harvey Harrison
2008-10-29 15:39 ` Joe Perches
2008-10-29 17:24 ` Harvey Harrison
2008-10-29 18:16 ` Joe Perches
2008-10-29 18:21 ` Harvey Harrison
2008-10-29 18:32 ` oh crap David Miller
2008-10-29 18:31 ` David Miller
2008-10-29 19:13 ` Joe Perches
2008-10-29 18:28 ` David Miller [this message]
2008-10-29 18:31 ` Harvey Harrison
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=20081029.112852.153175366.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=harvey.harrison@gmail.com \
--cc=joe@perches.com \
--cc=netdev@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 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).