git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: Schuyler Duveen <sky@columbia.edu>
Cc: git@vger.kernel.org
Subject: Re: [RFC] submodule+shallow clone feature request
Date: Wed, 10 Feb 2010 17:10:07 -0500	[thread overview]
Message-ID: <32541b131002101410j3c256dbeg9aa8bacde99886bb@mail.gmail.com> (raw)
In-Reply-To: <4B73277C.9010801@columbia.edu>

On Wed, Feb 10, 2010 at 4:39 PM, Schuyler Duveen <sky@columbia.edu> wrote:
> 2. Some way to specify an override on .gitmodules sources.  This is
> because our .gitmodules includes public, read-only sources (github),
> rather than our local repos we would prefer to deploy from (for the
> purpose of reliability).

You can already override this by editing .git/config after running
'git submodule init'.  Of course, doing so precludes using --recursive
in "git clone."

> I'm not well-versed in the git source code yet, but poking around
> suggests that this is doable.  Would a patch be well received (or does
> someone want to do it for me :-)

The git-submodule stuff is rarely maintained.  I expect patches that
improve it will meet with generally positive response, but it's
somewhat unlikely that anyone will write them for you.

Have fun,

Avery

  reply	other threads:[~2010-02-10 22:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 21:39 [RFC] submodule+shallow clone feature request Schuyler Duveen
2010-02-10 22:10 ` Avery Pennarun [this message]
2010-02-10 22:14 ` Junio C Hamano
2010-02-10 22:57   ` Johannes Schindelin
2010-02-10 23:09     ` Junio C Hamano
2010-02-10 23:59       ` Johannes Schindelin
2010-02-11  6:19         ` Re* " Junio C Hamano
2010-02-11  6:51           ` Peter Hutterer

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=32541b131002101410j3c256dbeg9aa8bacde99886bb@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sky@columbia.edu \
    /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).