From: Jens Lehmann <Jens.Lehmann@web.de>
To: Olaf Hering <olaf@aepfle.de>
Cc: Mikael Magnusson <mikachu@gmail.com>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: let git grep consider sub projects
Date: Wed, 08 Oct 2014 09:24:37 +0200 [thread overview]
Message-ID: <5434E6B5.3030605@web.de> (raw)
In-Reply-To: <20141008065947.GA22318@aepfle.de>
Am 08.10.2014 um 08:59 schrieb Olaf Hering:
> On Wed, Oct 08, Jens Lehmann wrote:
>
>> git foo && git submodule foreach --recursive git foo
>
> Looks like a submodule is yet another thing, or I have to learn what a
> submodule is:
>
> olaf@bax:~/xen $ find . -name .git
> ./.git
> ./tools/qemu-xen-dir-remote/.git
> ./tools/qemu-xen-traditional-dir-remote/.git
> ./tools/firmware/seabios-dir-remote/.git
> olaf@bax:~/xen $ git submodule foreach --recursive git show
> olaf@bax:~/xen $
>
> xen does essentially 'git clone $url1 dir/url1-dir;git clone $url2
> dir/url2-dir'. So the top level .git does not really know about
> dir/*-dir.
Okay, I just checked that xen doesn't use submodules but uses simple
embedded repos ignored by the .gitignore file. From a quick glance
it looks like handling the sub projects is scripted in the Makefiles.
This is perfectly fine, but then you can't really expect git commands
to know about these sub projects. Or am I missing something?
next prev parent reply other threads:[~2014-10-08 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 8:29 let git grep consider sub projects Olaf Hering
2014-10-07 18:25 ` Junio C Hamano
2014-10-07 19:12 ` Mikael Magnusson
2014-10-08 6:48 ` Jens Lehmann
2014-10-08 6:59 ` Olaf Hering
2014-10-08 7:24 ` Jens Lehmann [this message]
2014-10-08 7:31 ` Olaf Hering
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=5434E6B5.3030605@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mikachu@gmail.com \
--cc=olaf@aepfle.de \
/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;
as well as URLs for NNTP newsgroup(s).