On 11/07/2011 12:30 PM, Sasha Levin wrote: > On Mon, Nov 7, 2011 at 12:23 PM, Gerd Hoffmann <kra...@redhat.com> wrote: > > Hi, > > > >> It's not just about code, it's as much about culture and development > >> process. > > > > Indeed. The BSDs have both kernel and the base system in a single > > repository. There are probably good reasons for (and against) it. > > > > In Linux we don't have that culture. No tool (except perf) lives in the > > kernel repo. I fail to see why kvm-tool is that much different from > > udev, util-linux, iproute, filesystem tools, that it should be included. > > tools/power was merged in just 2 versions ago, do you think that > merging that was a mistake?
Things like tools/power may make sense, most of the code is tied to the kernel interfaces. tools/kvm is 20k lines and is likely to be 40k+ lines or more before it is generally usable. The proportion of the code that talks to the kernel is quite small. -- error compiling committee.c: too many arguments to function
