netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: nakam@linux-ipv6.org
Cc: usagi-core@linux-ipv6.org, herbert@gondor.apana.org.au,
	netdev@vger.kernel.org
Subject: Re: [PATCH] [XFRM] IPv6: Fix dst/routing check at transformation.
Date: Thu, 20 Dec 2007 19:50:54 -0800 (PST)	[thread overview]
Message-ID: <20071220.195054.23654691.davem@davemloft.net> (raw)
In-Reply-To: <200712211248.31508.nakam@linux-ipv6.org>

From: Masahide NAKAMURA <nakam@linux-ipv6.org>
Date: Fri, 21 Dec 2007 12:48:31 +0900

> My 5 patches for XFRM sent to netdev should be TOed to David, but it is not.
> 
> It does not seems that the command works for me.
> git-send-email --to "David S. Miller <davem@davemloft.net>" --to herbert@gondor.apana.org.au --cc...
> 
> Please see my patches, even it is not TOed to you.

All of your patches won't make it anywhere.

In the email headers my name shows up like this:

	David S. Miller

Email SMTP rules dictate that if special characters like
"." appear in the name it must be surrounded by double
quotes otherwise it is a syntax error.

This is a bug in git-send-email that I thought was fixed
by now.  Perhaps it is fixed in git mainline and not any
of the stable releases yet.

Perhaps you can submit them by hand until you resolve the
git-send-email problem?

Thanks.

  parent reply	other threads:[~2007-12-21  3:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21  3:40 [PATCH] [XFRM] IPv6: Fix dst/routing check at transformation Masahide NAKAMURA
2007-12-21  3:50 ` Herbert Xu
     [not found] ` <200712211248.31508.nakam@linux-ipv6.org>
2007-12-21  3:50   ` David Miller [this message]
2007-12-21  5:06     ` Masahide NAKAMURA
2007-12-21  5:09       ` (usagi-core 34097) " Masahide NAKAMURA
2007-12-21  4:41 ` David Miller

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=20071220.195054.23654691.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=nakam@linux-ipv6.org \
    --cc=netdev@vger.kernel.org \
    --cc=usagi-core@linux-ipv6.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).