From: maximilian attems <max@stro.at>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Guide on how to submit patches for linux-wireless
Date: Tue, 25 Sep 2007 18:50:47 +0200 [thread overview]
Message-ID: <20070925165047.GH19918@baikonur.stro.at> (raw)
In-Reply-To: <43e72e890709241209obc236eav5eca6c0828052ee1@mail.gmail.com>
On Mon, Sep 24, 2007 at 03:09:03PM -0400, Luis R. Rodriguez wrote:
> Here's a new guide to help developers write and submit patches
> specifically for linux-wireless:
>
> http://linuxwireless.org/en/developers/SubmittingPatches
>
> Luis
please drop the recommendation of the patch 0.
it is a pain not to have it in the start of a serries in git.
thanks
--
maks
next prev parent reply other threads:[~2007-09-25 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 19:09 Guide on how to submit patches for linux-wireless Luis R. Rodriguez
2007-09-24 19:39 ` Larry Finger
2007-09-24 19:43 ` Johannes Berg
2007-09-24 20:27 ` Luis R. Rodriguez
2007-09-25 4:35 ` Michael Renzmann
2007-09-25 11:41 ` Krzysztof Halasa
2007-09-25 16:50 ` maximilian attems [this message]
2007-09-25 18:18 ` Johannes Berg
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=20070925165047.GH19918@baikonur.stro.at \
--to=max@stro.at \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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