From: Greg KH <greg@kroah.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-usb-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH] USB changes for 2.5.58
Date: Thu, 16 Jan 2003 12:25:06 -0800 [thread overview]
Message-ID: <20030116202506.GF32697@kroah.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1030116150638.6851E-100000@gatekeeper.tmr.com>
On Thu, Jan 16, 2003 at 03:14:39PM -0500, Bill Davidsen wrote:
> On Wed, 15 Jan 2003, Greg KH wrote:
>
> Would it be possible to post patches in general instead of pointing to bk:
> links? Some people can't use bk and would like the patches (legal opinion,
> not technical issues).
All usb patches that are sent to Marcelo and Linus are posted to the
linux-usb-devel mailing list as responses to the BK posting. I'm not
sending them to lkml as that would just be annoying to the 99% of the
people on there.
I also put the patches sent in patch form in the:
kernel.org/pub/linux/kernel/people/gregkh/usb/...
directories.
Is that sufficient for those not willing/able to use bk?
thanks,
greg k-h
next prev parent reply other threads:[~2003-01-16 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 23:24 [BK PATCH] USB changes for 2.5.58 Greg KH
2003-01-16 20:14 ` Bill Davidsen
2003-01-16 20:25 ` Greg KH [this message]
2003-01-17 14:43 ` Bill Davidsen
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=20030116202506.GF32697@kroah.com \
--to=greg@kroah.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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