From: "Lars Hjemli" <hjemli@gmail.com>
To: "Sergio Callegari" <sergio.callegari@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git submodule when submodule is not a clone of a repository
Date: Fri, 18 Jan 2008 18:46:03 +0100 [thread overview]
Message-ID: <8c5c35580801180946q3ba824e2s4c32ac504166c684@mail.gmail.com> (raw)
In-Reply-To: <loom.20080118T171433-93@post.gmane.org>
On Jan 18, 2008 6:25 PM, Sergio Callegari <sergio.callegari@gmail.com> wrote:
> Would it make sense to have a git submodule update not try to fetch if there is
> no url defined, but still checkout the right commit for the submodule (rather
> than skipping the submodule at all) ?
Actually, we could (and probably should) teach git-submodule not to
fetch if the requested SHA1 is already available in the submodule, and
I guess this would solve the problem quite nicely for your usage.
But that will probably not happen before 1.5.4.
--
larsh
next prev parent reply other threads:[~2008-01-18 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 17:25 git submodule when submodule is not a clone of a repository Sergio Callegari
2008-01-18 17:46 ` Lars Hjemli [this message]
2008-01-18 23:26 ` 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=8c5c35580801180946q3ba824e2s4c32ac504166c684@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--cc=sergio.callegari@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).