From: Alex Riesen <raa.lkml@gmail.com>
To: VMiklos <vmiklos@frugalware.org>
Cc: skimo@liacs.nl, git@vger.kernel.org
Subject: Re: question about git-submodule
Date: Sun, 15 Jul 2007 15:50:57 +0200 [thread overview]
Message-ID: <20070715135057.GI2568@steel.home> (raw)
In-Reply-To: <20070715105450.GD7106@genesis.frugalware.org>
VMiklos, Sun, Jul 15, 2007 12:54:50 +0200:
> Na Sun, Jul 15, 2007 at 12:47:12PM +0200, Alex Riesen <raa.lkml@gmail.com> pisal(a):
> > to. Subprojects defined in such a loosely way are more flexible then
> > having git-pull fetch subprojects by default. Sometimes I even want be
> > _sure_ the subprojects are completely untouched (I have some critical
> > parts in them).
>
> Okay, but where can you overwrite that default? It would be nice to have
> a config variable for this or something like that.
It is not a default in a sense where it control the behaviour of a git
command. git pull just does not do anything to subprojects and you use
a separate command (git-submodule update, I believe) to update them.
That said, I never used the git-submodule, nor did I have an urge to.
As I said, I find it convenient enough as it is with git-add and
git-diff, checking out the subproject as needed. Have to be careful
about "git commit -a" (which I almost never use anyway) and haven't
had conflicts yet.
next prev parent reply other threads:[~2007-07-15 13:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 21:46 question about git-submodule VMiklos
2007-07-15 8:39 ` Sven Verdoolaege
2007-07-15 10:47 ` Alex Riesen
2007-07-15 10:54 ` VMiklos
2007-07-15 13:50 ` Alex Riesen [this message]
2007-07-15 13:54 ` VMiklos
2007-07-15 14:02 ` Sven Verdoolaege
2007-07-15 14:26 ` VMiklos
2007-07-15 14:48 ` Sven Verdoolaege
2007-07-15 15:05 ` VMiklos
2007-07-15 15:21 ` Sven Verdoolaege
2007-07-15 15:40 ` VMiklos
2007-07-15 21:45 ` Sven Verdoolaege
2007-07-15 22:29 ` VMiklos
2007-07-16 10:39 ` Sven Verdoolaege
2007-07-16 11:07 ` VMiklos
2007-07-15 11:51 ` Sven Verdoolaege
2007-07-15 13:42 ` Alex Riesen
2007-07-15 13:52 ` Sven Verdoolaege
2007-08-03 23:01 ` Eran Tromer
2007-08-05 14:59 ` Sven Verdoolaege
2007-08-06 17:23 ` Eran Tromer
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=20070715135057.GI2568@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=skimo@liacs.nl \
--cc=vmiklos@frugalware.org \
/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).