linux-kernel - Re: 2.6.19 -mm merge plans

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20060924142353.6c725128.seanlkml@sympatico.ca>
Date:	Sun, 24 Sep 2006 14:23:53 -0400
From:	Sean <seanlkml@...patico.ca>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	Lennert Buytenhek <buytenh@...tstofly.org>,
	Linus Torvalds <torvalds@...l.org>,
	Dave Jones <davej@...hat.com>,
	David Miller <davem@...emloft.net>, jeff@...zik.org,
	davidsen@....com, alan@...rguk.ukuu.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.19 -mm merge plans

On Sun, 24 Sep 2006 10:20:10 +0100
Russell King <rmk+lkml@....linux.org.uk> wrote:

> The point I'm making is that for some things, keeping the changes as
> patches until they're ready is far easier, more worthwhile and flexible
> than having them simmering in some git tree somewhere.

It's not really easier, just different.   Git allows you to make a 
"topic branch" to keep separate items that need to bake before going
upstream without being mixed in with all your other worked.  This
allows you to continue to pull in upstream changes to make sure that
the patch series still applies cleanly and doesn't need updates etc.

Of course you may be more comfortable with other tools, but Git _does_
make it easy and practical to do the same thing.

Sean
-
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/