linux-kernel - Re: Why not creating a GIT RT tree ?

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: <m3zlv1fnjj.fsf@lugabout.jhcloos.org>
Date:	Sat, 19 Jan 2008 22:39:12 +0000
From:	James Cloos <cloos@...loos.com>
To:	"Francis Moreau" <francis.moro@...il.com>
Cc:	rostedt@...dmis.org, linux-kernel@...r.kernel.org
Subject: Re: Why not creating a GIT RT tree ?

>>>>> "Francis" == Francis Moreau <francis.moro@...il.com> writes:

>> It is in the one-head per patch style, and has the single-file
>> patches applied rather than the quilt queue.

Francis> Why don't you have one commit per patch ?

I started it before they had the broken out patches and haven't spent
the time to put together a process for the broken out patches akin to
what I figured out for the all-in-one patches.

In other words, intertia.

-JimC
-- 
James Cloos <cloos@...loos.com>         OpenPGP: 1024D/ED7DAEA6
--
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/