linux-kernel - Re: Announce: Linux-next (Or Andrew's dream :-))

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Feb 2008 11:36:24 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	David Miller <davem@...emloft.net>
CC:	arjan@...radead.org, greg@...ah.com, sfr@...b.auug.org.au,
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
	linux-arch@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))

David Miller wrote:
> This is why, with the networking, we've just tossed all of the network
> driver stuff in there too.  I can rebase freely, remove changesets,
> rework them, etc. and this causes a very low amount of pain for Jeff
> Garzik and John Linville.

s/very low/not low/

Rebasing is always a pain, and John and I both agreed the other day that 
you do it too often.

I've complained about this before, too...  but figured this was just 
another thing I was getting ignored on, and so life moved on.  But don't 
try to sell rebasing as "low pain".

Rebasing makes the history all nice and pretty, but by totalling 
flattening the history, trashing all the commit ids (and rewriting 
associated metadata), you create obvious downstream problems.

Rebasing is  low impact only if you don't have git downstream people. 
Otherwise, you're just treating it as a useful quilt clone, really.

	Jeff

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