linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Change BCMRING maintainer
Date: Thu, 17 Jun 2010 19:40:22 +0100	[thread overview]
Message-ID: <20100617184022.GA7973@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <8628FE4E7912BF47A96AE7DD7BAC0AADDDC69DDF19@SJEXCHCCR02.corp.ad.broadcom.com>

On Thu, Jun 17, 2010 at 10:14:57AM -0700, JD (Jiandong) Zheng wrote:
> I know it is better to use git to create patch in the future and seems 
> I just need to clone linus' release tree 
> (git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git) 
> instead of arm linux tree (linux-arm.org/linux-2.6-stable.git) to 
> make change and create patches, is this correct understanding?

Note that the linux-arm tree is ARM Ltd's tree, and isn't a tree which
feeds directly into Linus' tree.  You can find that via
http://www.arm.linux.org.uk/developer/ but I suggest that you use
Linus' tree as a base line unless I have something which conflicts
in my tree.

I maintain three primary branches:
- master, for stuff scheduled for -rc
- devel, for stuff scheduled for the next merge window, and is unstable
  (iow, commits don't have a stable ID, so it is inadvisable to base
   work off this.)
- devel-stable, for stuff scheduled for the next merge window, where the
  commits are immutable.

      reply	other threads:[~2010-06-17 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 20:42 [PATCH] MAINTAINERS: Change BCMRING maintainer JD (Jiandong) Zheng
2010-06-16  2:17 ` Eric Miao
2010-06-16  2:39   ` Joe Perches
2010-06-16  2:58     ` Eric Miao
2010-06-16 16:49       ` JD (Jiandong) Zheng
2010-06-17  3:18         ` Eric Miao
2010-06-17 17:14           ` JD (Jiandong) Zheng
2010-06-17 18:40             ` Russell King - ARM Linux [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=20100617184022.GA7973@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).