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: <20060922170909.GH15032@redhat.com>
Date:	Fri, 22 Sep 2006 13:09:09 -0400
From:	Dave Jones <davej@...hat.com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	David Miller <davem@...emloft.net>,
	Russell King <rmk+kernel@....linux.org.uk>, davidsen@....com,
	torvalds@...l.org, alan@...rguk.ukuu.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.19 -mm merge plans

On Fri, Sep 22, 2006 at 12:29:21PM -0400, Jeff Garzik wrote:
 > 
 > NOTE:  Your mailer generates bogus Mail-Followup-To headers, and you 
 > snipped rmk from the To/CC.

Hmm, curious. I'll file a bug. 

 > > 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.
 
Sorry, terminology confusion. I rarely throw away a tree and start afresh,
I meant of course just updating to linus' latest.  This may explain the
my lack of understanding over Russell's issues.

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