All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Wolfgang Mauerer <wolfgang.mauerer@siemens.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/2] kvm-kmod: Use the main development tree of kvm as Linux submodule
Date: Thu, 22 Oct 2009 18:17:36 +0200	[thread overview]
Message-ID: <4AE085A0.7030300@redhat.com> (raw)
In-Reply-To: <4AE084B8.2050902@siemens.com>

On 10/22/2009 06:13 PM, Wolfgang Mauerer wrote:
> Hi,
>
> Avi Kivity wrote:
>    
>> On 10/20/2009 02:11 PM, wolfgang.mauerer@siemens.com wrote:
>>      
>>> From: Wolfgang Mauerer<wolfgang.mauerer@siemens.com>
>>>
>>> Most people won't have the sources installed in the path
>>> that is the current default setting.
>>>
>>> --- a/.gitmodules
>>> +++ b/.gitmodules
>>> @@ -1,3 +1,3 @@
>>>    [submodule "linux-2.6"]
>>>    	path = linux-2.6
>>> -	url = ../kvm.git
>>> +	url = git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
>>>
>>>        
>> '../kvm.git' is interpreted relative to the origin url, which is usually
>> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm-kmod.git, so it
>> all works out (including when kvm-kmod.git was cloned using the http
>> protocol, or from a mirror).
>>
>> What exactly are you trying to fix?
>>      
> consider that you clone kvm-kmod from your repo and
> then create local clones from which you do the build. If you don't
> happen to have /path/to/my/kvm-kmod/../kvm, then the relative
> submodule URL won't work, but the absolute one will.
>    

Typically you create the clones using 'git submodule init && git 
submodule update', not clone them manually.

> Since the absolute URL wouldn't break anything AFAIK, but
> makes this scenario work, I'd favour it, although my
> life would not be much worse with the relative default
> URL ;-)
>    

You can still make it work by editing .git/config and updating the URLs.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-10-22 16:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 12:11 [PATCH 1/2] kvm-kmod: Use the main development tree of kvm as Linux submodule wolfgang.mauerer
2009-10-20 12:11 ` [PATCH 2/2] kvm-kmod: Document the build process wolfgang.mauerer
2009-10-21 10:43   ` Dietmar Maurer
2009-10-21 14:20     ` Wolfgang Mauerer
2009-10-22 20:54       ` Dietmar Maurer
2009-10-23  7:50         ` Jan Kiszka
2009-11-12 17:35           ` [PATCH] kvm-kmod: Document the build process (take 2) Wolfgang Mauerer
2009-11-14  9:08             ` Jan Kiszka
2009-10-22 15:15 ` [PATCH 1/2] kvm-kmod: Use the main development tree of kvm as Linux submodule Avi Kivity
2009-10-22 16:13   ` Wolfgang Mauerer
2009-10-22 16:17     ` Avi Kivity [this message]
2009-10-22 16:25       ` Wolfgang Mauerer
2009-10-22 16:35         ` Avi Kivity

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=4AE085A0.7030300@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=wolfgang.mauerer@siemens.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.