Re: [PATCH] KVM: add localversion to avoid confusion and conflicts

From: Jaswinder Singh Rajput
Date: Fri May 29 2009 - 04:46:42 EST


On Fri, 2009-05-29 at 09:48 +0200, Christian BorntrÃger wrote:
> Am Freitag 29 Mai 2009 09:18:14 schrieb Jaswinder Singh Rajput:
> > Adding localversion avoids confusion in kernel images :
> >
> > like Linux version 2.6.30-rc7 does not tell whether it is linus or kvm
> > kernel.
> >
> > By adding localversion it tells :
> >
> > Linux version 2.6.30-rc7-kvm , any doubt ;-)
> > I am inspired by Ingo's -tip, I am sure Ingo will tell more advantages,
> > if these are not enough :-)
> [...]
> > diff --git a/localversion-kvm b/localversion-kvm
> > new file mode 100644
> > index 0000000..d969ff0
> > --- /dev/null
> > +++ b/localversion-kvm
> > @@ -0,0 +1 @@
> > +-kvm
>
> NAK from my side. If you need a distinction, there is always
> CONFIG_LOCALVERSION_AUTO. If you need this kind of prefix, there is always
> CONFIG_LOCALVERSION.
>

Here is NAK for your NAK from my side.

This patch is only for KVM tree and not for linus tree.

Lets assume 100 developers are working on kvm tree and they use kvm tree
on 2 PCs. So count becomes 200.

Like in my case I have dozen of kernel trees so I keep on swapping
config between kernels. And I also need to test config from various
users. So this count is countless.
I think this is the biggest point for adding localversion in -tip.
It seems Ingo is busy in perfcounter stuff otherwise he will explain you
more advantages.

In the least case, Can you differentiate between 1 and 200 ?

So by adding this patch we can save lot of developer's time.

--
JSR

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/