From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Tony Vroon <tony@linx.net>
Cc: "Luis Rodriguez" <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Diego E. 'Flameeyes' Pettenò" <flameeyes@gmail.com>
Subject: Re: [PATCH] CRDA 0.1.0: Fix building with --as-needed
Date: Sat, 24 Jan 2009 12:40:22 -0800 [thread overview]
Message-ID: <20090124204022.GD22475@tesla> (raw)
In-Reply-To: <1232826895.19384.3.camel@localhost>
On Sat, Jan 24, 2009 at 11:54:55AM -0800, Tony Vroon wrote:
> It seems mails from Flameeyes just do not make it through to
> linux-wireless, so there it is. Please apply this and consider releasing
> 1.0.1 (without a v in the tarball name, if at all possible).
Thanks! Can you please resend without signing the patch e-mail?
http://wireless.kernel.org/en/developers/Documentation/SubmittingPatches#Priortosendingpatches
Luis
prev parent reply other threads:[~2009-01-24 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 19:54 [PATCH] CRDA 0.1.0: Fix building with --as-needed Tony Vroon
2009-01-24 20:40 ` Luis R. Rodriguez [this message]
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=20090124204022.GD22475@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=flameeyes@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tony@linx.net \
/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).