public inbox for kvm@vger.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:35:50 +0200	[thread overview]
Message-ID: <4AE089E6.4000909@redhat.com> (raw)
In-Reply-To: <4AE0876A.5060005@siemens.com>

On 10/22/2009 06:25 PM, Wolfgang Mauerer wrote:
>
>    
>>> 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.
>>      
> But that refers to linux-2.6/, I suppose, while I was talking
> about kvm-kmod.
>    

Oh.  If you create local clones for kvm-kmod.git, also create local 
clones for kvm.git.  I'd expect the submodule to use the local clone 
(for example, if I don't have access to the external hosting).

> that's certainly true. I'd say it's a matter of taste, so
> I'll just add a hint about .git/config to the README and leave
> .gitmodules unmolested in the future.
>    

Relative paths are a requirement for http: access, which is needed from 
certain corporate firewalls, so it will have to stay.

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


      reply	other threads:[~2009-10-22 16:35 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
2009-10-22 16:25       ` Wolfgang Mauerer
2009-10-22 16:35         ` Avi Kivity [this message]

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=4AE089E6.4000909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox