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] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1308211502141.4089@ionos.tec.linutronix.de>
Date:	Wed, 21 Aug 2013 15:04:21 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Daniel Lezcano <daniel.lezcano@...aro.org>
cc:	Ingo Molnar <mingo@...nel.org>,
	John Stultz <john.stultz@...aro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Can you act as backup for timers/core and timers/urgent ?

On Tue, 20 Aug 2013, Daniel Lezcano wrote:
> Is it possible you act as a backup and you update timers/core which is
> in -rc1 to the latest -rc where I will rebase my tree on and resend a
> pull request with all the patches in (previous PR should be ignored) ?

I updated to linus latest and merged your tree. Rebasing is not what
we want. The patches were done against a certain state and tested
against that. So we want to preserve that and not some random untested
rebase conglomerate. Please check the conflict resolution once it hits
the public servers.

Thanks,

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ