| 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
| ||
|
Date: Sat, 19 Jan 2008 21:17:15 +0100 From: "Francis Moreau" <francis.moro@...il.com> To: "James Cloos" <cloos@...loos.com> Cc: rostedt@...dmis.org, linux-kernel@...r.kernel.org Subject: Re: Why not creating a GIT RT tree ? Hello, On Jan 18, 2008 10:59 PM, James Cloos <cloos@...loos.com> wrote: > >>>>> "Francis" == Francis Moreau <francis.moro@...il.com> writes: > > Francis> I can't find a rt tree anywhere and all new rt release spoke > Francis> about a patchset to apply on mainline kernels. > > It is not perfect, but I do have a git repo of the rt history-of-patches > up at: > > git://git.kernel.org/pub/scm/linux/kernel/git/cloos/rt-2.6.git > http://www.kernel.org/pub/scm/linux/kernel/git/cloos/rt-2.6.git > > Gitweb URL is: > > http://git.kernel.org/?p=linux/kernel/git/cloos/rt-2.6.git > > It is in the one-head per patch style, and has the single-file patches > applied rather than the quilt queue. Why don't you have one commit per patch ? Thanks -- Francis -- 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