From: Jeff Garzik <jgarzik@pobox.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: netdev@oss.sgi.com, "David S.Miller" <davem@davemloft.net>
Subject: Re: [PATCH] Merge p80211 to ieee80211 subsystem
Date: Fri, 25 Mar 2005 04:10:21 -0500 [thread overview]
Message-ID: <4243D57D.9050008@pobox.com> (raw)
In-Reply-To: <1111740953.17276.84.camel@debian.sh.intel.com>
It looks like your mailer word-wrapped the patch, making it impossible
to apply. Evolution is, unfortunately, notorious for this.
I recommend using the /usr/sbin/sendmail technique described in
http://lkml.org/lkml/2005/2/24/3
to send patches.
The sendmail technique guarantees your patch will not be corrupted by
your MUA, and as a bonus, avoids using attachments (attachments are a
bit annoying when quoting+replying to patches).
Regards,
Jeff
next prev parent reply other threads:[~2005-03-25 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 8:55 [PATCH] Merge p80211 to ieee80211 subsystem Zhu Yi
2005-03-25 9:10 ` Jeff Garzik [this message]
2005-03-27 2:37 ` Jouni Malinen
2005-03-28 7:19 ` Zhu Yi
2005-03-28 14:53 ` Jouni Malinen
2005-03-28 19:47 ` jamal
-- strict thread matches above, loose matches on Subject: below --
2005-03-25 9:41 Zhu, Yi
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=4243D57D.9050008@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=yi.zhu@intel.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).