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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <47B1E14E.2010207@garzik.org>
Date:	Tue, 12 Feb 2008 13:11:26 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	"John W. Linville" <linville@...driver.com>
CC:	David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))

John W. Linville wrote:
> FWIW, I definitely have a (vocal minority) group of contributors
> who resent all the rebasing.  There may be a few cases of 'vanity'
> represented here, but there are definitely reasonable complaints about
> not being able to do simple pulls to stay up-to-date and/or having
> to rebase before they can send patches to me.  FWIW, I think it might
> save a bit of my time as well, although I have become pretty good and
> "riding the tide" of rebasing... :-(


Definitely...  that is the sort of stuff that upstream folks never see 
when they rebase -- it causes an explosion of downstream rebasing, where 
each rebase must wait for the one-step-up upstream to rebase, before 
patches can be sent.  It's easy for the rebasing to get exponential 
quickly, the more downstream levels you have.

	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/