Hi all,
Thanks to a tonne of help (and friendly nagging!) from Andre, I'm
pleased to announce a stand-alone repository for kvmtool:
git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git
This is a follow-up from a previous thread[1] where we concluded that
this was the right way to
On Mon, Feb 23, 2015 at 05:23:58PM +, Pekka Enberg wrote:
> On 2/18/15 5:50 PM, Will Deacon wrote:
> > Thanks for doing this. Since it looks unlikely that kvmtool will ever be
> > merged back into the kernel tree, it makes sense to cut the dependency
> > in my opinion.
>
> I am certainly OK
On Mon, Feb 23, 2015 at 05:23:58PM +, Pekka Enberg wrote:
On 2/18/15 5:50 PM, Will Deacon wrote:
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it makes sense to cut the dependency
in my opinion.
I am certainly OK with a
Hi all,
Thanks to a tonne of help (and friendly nagging!) from Andre, I'm
pleased to announce a stand-alone repository for kvmtool:
git://git.kernel.org/pub/scm/linux/kernel/git/will/kvmtool.git
This is a follow-up from a previous thread[1] where we concluded that
this was the right way to
On 2/26/15 1:02 PM, Alex Bennée wrote:
If you can have it all it would be nice to preserve buildability all
through your history for bisecting (and the moon on a stick please ;-)
Is the dependency on the kernel sources something that has been stable
over the projects history or something that's
On 2/26/15 1:02 PM, Alex Bennée wrote:
If you can have it all it would be nice to preserve buildability all
through your history for bisecting (and the moon on a stick please ;-)
Is the dependency on the kernel sources something that has been stable
over the projects history or something that's
Andre Przywara writes:
> Hi Will,
>
> On 18/02/15 15:50, Will Deacon wrote:
>> Hi Andre,
>>
>> Thanks for doing this. Since it looks unlikely that kvmtool will ever be
>> merged back into the kernel tree, it makes sense to cut the dependency
>> in my opinion.
>>
>
> P.S. Although both
Andre Przywara andre.przyw...@arm.com writes:
Hi Will,
On 18/02/15 15:50, Will Deacon wrote:
Hi Andre,
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it makes sense to cut the dependency
in my opinion.
snip
P.S. Although
On Mon, Feb 23, 2015 at 05:23:58PM +, Pekka Enberg wrote:
> Hi,
Hi Pekka,
Sorry for the delay, I've been away from email for a few days.
> On 2/18/15 5:50 PM, Will Deacon wrote:
> > Thanks for doing this. Since it looks unlikely that kvmtool will ever be
> > merged back into the kernel
On Mon, Feb 23, 2015 at 05:23:58PM +, Pekka Enberg wrote:
Hi,
Hi Pekka,
Sorry for the delay, I've been away from email for a few days.
On 2/18/15 5:50 PM, Will Deacon wrote:
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it
Hi,
On 2/18/15 5:50 PM, Will Deacon wrote:
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it makes sense to cut the dependency
in my opinion.
I am certainly OK with a standalone repository which preserves the
history. Will, would
Hi,
On Thu, Feb 19, 2015 at 05:56:45AM -0500, Sasha Levin wrote:
[...]
>
> What inconvenience is caused by having it sit inside the kernel tree
> beyond an increased requirement in disk space?
>
FWIW: I would prefer seeing this outside the kernel tree; I think it is
slightly confusing to keep
On Thu, Feb 19, 2015 at 05:56:45AM -0500, Sasha Levin wrote:
> What inconvenience is caused by having it sit inside the kernel tree
> beyond an increased requirement in disk space?
I've come across this problem with the perf tools - luckily, the perf
tools allow the source to be exported from the
Hi Sasha,
thanks for taking a look!
On 19/02/15 10:56, Sasha Levin wrote:
> On 02/13/2015 05:39 AM, Andre Przywara wrote:
>> Hi,
>>
>> as I found it increasingly inconvenient to use kvmtool[1] as part of a
>> Linux repository, I decided to give it a go and make it a stand-alone
>> project. So I
Hi Will,
On 18/02/15 15:50, Will Deacon wrote:
> Hi Andre,
>
> Thanks for doing this. Since it looks unlikely that kvmtool will ever be
> merged back into the kernel tree, it makes sense to cut the dependency
> in my opinion.
>
> On Fri, Feb 13, 2015 at 10:39:33AM +, Andre Przywara wrote:
Hi Will,
On 18/02/15 15:50, Will Deacon wrote:
Hi Andre,
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it makes sense to cut the dependency
in my opinion.
On Fri, Feb 13, 2015 at 10:39:33AM +, Andre Przywara wrote:
as I
Hi Sasha,
thanks for taking a look!
On 19/02/15 10:56, Sasha Levin wrote:
On 02/13/2015 05:39 AM, Andre Przywara wrote:
Hi,
as I found it increasingly inconvenient to use kvmtool[1] as part of a
Linux repository, I decided to give it a go and make it a stand-alone
project. So I filtered
On Thu, Feb 19, 2015 at 05:56:45AM -0500, Sasha Levin wrote:
What inconvenience is caused by having it sit inside the kernel tree
beyond an increased requirement in disk space?
I've come across this problem with the perf tools - luckily, the perf
tools allow the source to be exported from the
Hi,
On Thu, Feb 19, 2015 at 05:56:45AM -0500, Sasha Levin wrote:
[...]
What inconvenience is caused by having it sit inside the kernel tree
beyond an increased requirement in disk space?
FWIW: I would prefer seeing this outside the kernel tree; I think it is
slightly confusing to keep it
Hi,
On 2/18/15 5:50 PM, Will Deacon wrote:
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it makes sense to cut the dependency
in my opinion.
I am certainly OK with a standalone repository which preserves the
history. Will, would
On 02/13/2015 05:39 AM, Andre Przywara wrote:
> Hi,
>
> as I found it increasingly inconvenient to use kvmtool[1] as part of a
> Linux repository, I decided to give it a go and make it a stand-alone
> project. So I filtered all the respective commits, adjusted the paths in
> there (while keeping
On 02/13/2015 05:39 AM, Andre Przywara wrote:
Hi,
as I found it increasingly inconvenient to use kvmtool[1] as part of a
Linux repository, I decided to give it a go and make it a stand-alone
project. So I filtered all the respective commits, adjusted the paths in
there (while keeping
Hi Andre,
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it makes sense to cut the dependency
in my opinion.
On Fri, Feb 13, 2015 at 10:39:33AM +, Andre Przywara wrote:
> as I found it increasingly inconvenient to use kvmtool[1] as
Hi Andre,
Thanks for doing this. Since it looks unlikely that kvmtool will ever be
merged back into the kernel tree, it makes sense to cut the dependency
in my opinion.
On Fri, Feb 13, 2015 at 10:39:33AM +, Andre Przywara wrote:
as I found it increasingly inconvenient to use kvmtool[1] as
On 13.02.2015 15:40, Andre Przywara wrote:
> Ciao Claudio,
>
> On 13/02/15 14:30, Claudio Fontana wrote:
>> Hello Andre,
>>
>> On 13.02.2015 11:39, Andre Przywara wrote:
>>> Hi,
>>>
>>> as I found it increasingly inconvenient to use kvmtool[1] as part of a
>>> Linux repository, I decided to give
Ciao Claudio,
On 13/02/15 14:30, Claudio Fontana wrote:
> Hello Andre,
>
> On 13.02.2015 11:39, Andre Przywara wrote:
>> Hi,
>>
>> as I found it increasingly inconvenient to use kvmtool[1] as part of a
>> Linux repository, I decided to give it a go and make it a stand-alone
>> project. So I
Hello Andre,
On 13.02.2015 11:39, Andre Przywara wrote:
> Hi,
>
> as I found it increasingly inconvenient to use kvmtool[1] as part of a
> Linux repository, I decided to give it a go and make it a stand-alone
> project. So I filtered all the respective commits, adjusted the paths in
> there
Hi,
as I found it increasingly inconvenient to use kvmtool[1] as part of a
Linux repository, I decided to give it a go and make it a stand-alone
project. So I filtered all the respective commits, adjusted the paths in
there (while keeping authorship and commit date, of course) and then
added the
Hi,
as I found it increasingly inconvenient to use kvmtool[1] as part of a
Linux repository, I decided to give it a go and make it a stand-alone
project. So I filtered all the respective commits, adjusted the paths in
there (while keeping authorship and commit date, of course) and then
added the
Hello Andre,
On 13.02.2015 11:39, Andre Przywara wrote:
Hi,
as I found it increasingly inconvenient to use kvmtool[1] as part of a
Linux repository, I decided to give it a go and make it a stand-alone
project. So I filtered all the respective commits, adjusted the paths in
there (while
Ciao Claudio,
On 13/02/15 14:30, Claudio Fontana wrote:
Hello Andre,
On 13.02.2015 11:39, Andre Przywara wrote:
Hi,
as I found it increasingly inconvenient to use kvmtool[1] as part of a
Linux repository, I decided to give it a go and make it a stand-alone
project. So I filtered all the
On 13.02.2015 15:40, Andre Przywara wrote:
Ciao Claudio,
On 13/02/15 14:30, Claudio Fontana wrote:
Hello Andre,
On 13.02.2015 11:39, Andre Przywara wrote:
Hi,
as I found it increasingly inconvenient to use kvmtool[1] as part of a
Linux repository, I decided to give it a go and make it a
32 matches
Mail list logo
