From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Opinion about Linux Foundation courses
Date: Fri, 10 Sep 2010 17:09:13 +0000 [thread overview]
Message-ID: <20100910170913.GC6193@kroah.com> (raw)
In-Reply-To: <AANLkTikugt28Lsf9wgCyOD=t4SK4pMyCNxCU5Yahs_nz@mail.gmail.com>
On Fri, Sep 10, 2010 at 03:31:14PM +0530, Rahul Ruikar wrote:
> Thanks Greg,
> I have query related to which git tree to take as reference for bug
> fix / code review . .etc
It depends on the subsystem you are concerned about.
> I am aware of this one
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6.git
That is for no one to use, didn't you notice the description of it:
"Junk tree, do not use".
I use that ONLY to send patches to Linus, so consider it a private tree
for just me to use occasionally in this manner.
> I mean developers who post their patches in "linux-usb" mailing
> list.. Do they always refer to above git tree. ?
No.
See the MAINTAINERS file for the locations of the developer trees for
the different subsystems, they are all specified there.
If you want to see all of the developer trees together, use the
linux-next tree, that is what it is there for.
If you want to report bugs, they can be reported against any tree you
find :)
But most importantly, test Linus's tree, that is where we care about
bugs the most.
Hope this helps,
greg k-h
prev parent reply other threads:[~2010-09-10 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 22:54 Opinion about Linux Foundation courses Andre Nogueira
2010-09-08 0:44 ` Greg KH
2010-09-09 1:15 ` Greg KH
2010-09-09 10:45 ` Andre Nogueira
2010-09-09 13:08 ` Kevin McKinney
2010-09-09 13:53 ` Maciej Grela
2010-09-09 14:28 ` Jason
2010-09-09 15:34 ` Kevin McKinney
2010-09-09 16:23 ` Jason
2010-09-09 20:28 ` Greg KH
2010-09-10 10:13 ` Rahul Ruikar
2010-09-10 17:09 ` Greg KH [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=20100910170913.GC6193@kroah.com \
--to=greg@kroah.com \
--cc=kernel-janitors@vger.kernel.org \
/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