From: Sven Verdoolaege <skimo@kotnet.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: VMiklos <vmiklos@frugalware.org>, git@vger.kernel.org
Subject: Re: question about git-submodule
Date: Sun, 15 Jul 2007 13:51:48 +0200 [thread overview]
Message-ID: <20070715115148.GD999MdfPADPa@greensroom.kotnet.org> (raw)
In-Reply-To: <20070715104712.GF2568@steel.home>
On Sun, Jul 15, 2007 at 12:47:12PM +0200, Alex Riesen wrote:
> Count me out. Junio convinced me instead and having tried the
> subprojects I find it really convenient: I can choose when and what
> should be updated and I can see what _can_ be updated, iff I decide
> to. Subprojects defined in such a loosely way are more flexible then
> having git-pull fetch subprojects by default.
I agree that fetching should probably be left as a separate operation,
but if you have all the data, then I find it very inconvenient that
every time you switch to a different commit you have to update
all the subprojects separately too.
Did you change your mind about this part too?
> Sometimes I even want be
> _sure_ the subprojects are completely untouched (I have some critical
> parts in them).
The update in the superproject would fail if the subproject is dirty
(just as with files.)
skimo
next prev parent reply other threads:[~2007-07-15 11: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
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 [this message]
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=20070715115148.GD999MdfPADPa@greensroom.kotnet.org \
--to=skimo@kotnet.org \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--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).