From: "John W. Linville" <linville@tuxdriver.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: yi.zhu@intel.com, linux-wireless@vger.kernel.org
Subject: Re: Please pull patch-bomb for iwlwifi
Date: Wed, 25 Jul 2007 15:01:22 -0400 [thread overview]
Message-ID: <20070725190122.GG7093@tuxdriver.com> (raw)
In-Reply-To: <46A75CD9.9050100@garzik.org>
On Wed, Jul 25, 2007 at 10:23:21AM -0400, Jeff Garzik wrote:
> Two suggestions:
>
> 1) You should post patches to the list for review. Yes, even if there
> are 117 of them. That is acceptable -- and encouraged -- mailing list
> etiquette.
Sure...even better, of course, would to post them as they are written
instead of saving them for one big sweep...
> 2) I would recommend submitting via git. Auke @ Intel does this with
> e100/e1000/etc. stuff and it works great.
>
> The main suggestion is #1, since it is important to post patches to
> linux-wireless. #2 is more in the realm of linville's preference.
Submissions via git are fine in general -- I do reserve the right to
rebase them, edit commit comments, etc.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-07-25 19:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 8:57 Please pull patch-bomb for iwlwifi Zhu Yi
2007-07-25 9:48 ` Andy Green
2007-07-25 14:23 ` Jeff Garzik
2007-07-25 14:43 ` Holger Schurig
2007-07-25 15:12 ` Andy Green
2007-07-25 15:15 ` Jeff Garzik
2007-07-25 15:35 ` Christoph Hellwig
2007-07-25 20:40 ` Dan Williams
2007-07-25 19:01 ` John W. Linville [this message]
2007-07-25 21:20 ` Jeff Garzik
2007-07-25 20:07 ` John W. Linville
2007-07-25 21:00 ` Tomas Winkler
2007-07-25 21:26 ` Jeff Garzik
2007-07-25 21:53 ` Tomas Winkler
2007-07-26 1:55 ` Zhu Yi
-- strict thread matches above, loose matches on Subject: below --
2007-06-08 22:15 James Ketrenos
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=20070725190122.GG7093@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.