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

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

Date:	Fri, 22 Sep 2006 12:29:21 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Dave Jones <davej@...hat.com>, David Miller <davem@...emloft.net>,
	Russell King <rmk+kernel@....linux.org.uk>
CC:	davidsen@....com, torvalds@...l.org, alan@...rguk.ukuu.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.19 -mm merge plans

NOTE:  Your mailer generates bogus Mail-Followup-To headers, and you 
snipped rmk from the To/CC.

Dave Jones wrote:
> Hmm. Some trees do seem to get pulled more often than others.
> Linus, is there a upper limit on the number of times you want
> to see pull requests? It strikes me as odd, so I'm wondering
> if there are some crossed wires here.

Not speaking for Linus, but in general it seems like the more pull 
requests you send (within reason), the more pulls that occur.  Russell 
and DaveM certainly seem to send frequent, successful pull requests.

> Has Andrew commented on why this is proving to be more of a problem?
> I've done regular rebases of cpufreq/agpgart (admittedly, they don't
> reject hardly ever unless Len has ACPI bits touching cpufreq) without
> causing too much headache.

Rebasing _inevitably_ causes more headaches than a simple tree update, 
for any downstream consumer of your tree(s).  It is best to avoid wanton 
rebasing.

Think about it:  if someone is pulling and merging your tree, all of a 
sudden, without warning, the entire hash history is rewritten.  So 
rather than a Nice and Friendly minor update, the next time they pull 
your stuff, the downstream user is forced to suffer through either (a) a 
painful merge, or (b) back out your last tree (ugh!) and redo things 
from scratch.

Rebasing might make a pretty history, but it is _not_ fun for random 
consumers of your trees.  It basically punishes people for following 
your tree -- not something you want to do.

	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/