linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linux PM list <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [Announce] linux-pm tree changes
Date: Tue, 24 Jan 2012 23:56:04 +0100	[thread overview]
Message-ID: <201201242356.04244.rjw@sisk.pl> (raw)

Hi,

I'd like you to know some workflow changes regarding the linux-pm tree.

Since it's now possible to create signed tags for Linus to pull from, I won't
need the 'pm-for-linus' branch any more and it's gone.  The 'pm-fixes' branch
is gone too and replaced by the 'fixes' branch (which currently contains the
same material as master).

The idea is that the main development is going to happen in the 'master'
branch, which is not going to be rebased and the Linus' tree will be merged
into it from time to time (most of the time when the 'master' branch can be
fast-forwarded to it).  The 'fixes' branch will be used for pushing urgent 
stuff that must go in before the new material in the 'master' branch.

The linux-next branch is going to be based on top of the master branch
with the 'fixes' branch merged into it and will contain additional new
material that hasn't been added to the master branch yet.  Every patch
going through linux-pm has to spend some time in the linux-next branch
alone before it is added to the master (or 'fixes') branch (some super-urgent
fixes may go directly to the 'fixes' branch, though).

Topic branches are all gone now and they will be re-created as needed.

If you have any questions, please ask.

Thanks,
Rafael

             reply	other threads:[~2012-01-24 22:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 22:56 Rafael J. Wysocki [this message]
2012-01-25 19:03 ` [Announce] linux-pm tree changes Paul Gortmaker
2012-01-25 22:32   ` Rafael J. Wysocki

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=201201242356.04244.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@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;
as well as URLs for NNTP newsgroup(s).