lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 24 Jan 2012 23:56:04 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Linux PM list <linux-pm@...r.kernel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: [Announce] linux-pm tree changes

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ