git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: let git grep consider sub projects

From
Jens Lehmann <jens.lehmann@web.de>
Date
Oct 8, 2014, 07:24 UTC
Message-ID
<5434E6B5.3030605@web.de>
In-Reply-To
<20141008065947.GA22318@aepfle.de>
Am 08.10.2014 um 08:59 schrieb Olaf Hering:
Show 18 quoted lines
> 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?

Previous: Olaf HeringNext: Olaf Hering
Message 6 of 7 in “let git grep consider sub projects”
  1. Olaf HeringOct 7, 2014
  2. Junio C HamanoOct 7, 2014
  3. Mikael MagnussonOct 7, 2014
  4. Jens LehmannOct 8, 2014
  5. Olaf HeringOct 8, 2014
  6. Jens LehmannOct 8, 2014
  7. Olaf HeringOct 8, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.