git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lars Hjemli" <hjemli@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Alexander Litvinov" <litvinov2004@gmail.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.2-rc3
Date: Fri, 11 May 2007 13:08:36 +0200	[thread overview]
Message-ID: <8c5c35580705110408g7068e917lb672e1ac56f2c84c@mail.gmail.com> (raw)
In-Reply-To: <7v1whnesyn.fsf@assigned-by-dhcp.cox.net>

On 5/11/07, Junio C Hamano <junkio@cox.net> wrote:
> Alexander Litvinov <litvinov2004@gmail.com> writes:
>
> > I have tried your test and found that cloning such repo does not clone
> > subprojects. Only empty dir 'sub' is being cloned.
>
> Yes, that is pretty much intentional.  Having a link for higher
> layer tools can use (i.e. tree objects can contain 160000 mode
> "gitlinks" to subproject commit objects) while not considering
> such linkage part of the reachability is the whole point of
> plumbing level subproject support.  It allows people not to
> download repositories of uninteresting subprojects.  Higher
> layer tools such as clone/checkout/diff could be instructed
> (currently they cannot be, though) to recurse into subproject
> directories if the user wants to.

fwiw: I just released cgit 0.3, which includes a script
(submodules.sh) used to initialize, update and check status of
submodules. It uses the file .gitmodules to map between submodule path
and git repository url (cgit now uses git as a submodule).

You can clone the repo here:

  git://hjemli.net/pub/git/cgit

just look at the files here:

  http://hjemli.net/git/cgit/

--
larsh

  reply	other threads:[~2007-05-11 11:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11  0:23 [ANNOUNCE] GIT 1.5.2-rc3 Junio C Hamano
2007-05-11  3:23 ` Alexander Litvinov
2007-05-11  4:28   ` Junio C Hamano
2007-05-11  6:30     ` Alexander Litvinov
2007-05-11  7:10       ` Junio C Hamano
2007-05-11 11:08         ` Lars Hjemli [this message]
2007-05-11  9:02     ` Martin Waitz
2007-05-11 17:10       ` Junio C Hamano

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=8c5c35580705110408g7068e917lb672e1ac56f2c84c@mail.gmail.com \
    --to=hjemli@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=litvinov2004@gmail.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;
as well as URLs for NNTP newsgroup(s).