From: Avi Kivity <avi@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Jaswinder Singh Rajput" <jaswinder@kernel.org>,
"Christian Bornträger" <borntraeger@de.ibm.com>,
"Ingo Molnar" <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
"KVM list" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: add localversion to avoid confusion and conflicts
Date: Mon, 01 Jun 2009 22:48:52 +0300 [thread overview]
Message-ID: <4A2430A4.1080908@redhat.com> (raw)
In-Reply-To: <20090601192624.GA32428@goodmis.org>
Steven Rostedt wrote:
>
>> 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.
>>
>
> No this patch wastes a lot of developers time. If we accept it, than any
> patch that is added after it will need to be rebased before going to
> Linus. Unless KVM is made up of a bunch of branches like tip is, this will become
> more of a hassle than a benefit.
>
kvm.git for-linus branches are rebased anyway, since I fold patches that
fix or revert other patches. I also (rarely) delay some patches in my
tree but submit others that came later.
localversion would show up in linux-next, not sure if that's a problem.
On the other hand, I'm not sure what it's worth.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-06-01 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 7:18 [PATCH] KVM: add localversion to avoid confusion and conflicts Jaswinder Singh Rajput
2009-05-29 7:48 ` Christian Bornträger
2009-05-29 8:43 ` Jaswinder Singh Rajput
2009-05-29 9:29 ` Christian Bornträger
2009-06-01 19:26 ` Steven Rostedt
2009-06-01 19:48 ` Avi Kivity [this message]
2009-06-01 19:53 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A2430A4.1080908@redhat.com \
--to=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=jaswinder@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox