From: "Fabian Franz" <FabianFranz@gmx.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] submodule: add --no-fetch parameter to update command
Date: Sat, 07 Feb 2009 16:44:25 +0100 [thread overview]
Message-ID: <20090207154425.325390@gmx.net> (raw)
In-Reply-To: <8c5c35580902061001m6259d4ebt1c0dea7691b0a5dc@mail.gmail.com>
> Fabian Franz <git@fabian-franz.de> writes:
>
> > git submodule update --no-fetch makes it possible to use git submodule
> > update in complete offline mode by not fetching new revisions.
> >
> > This does make sense in the following setup:
> >
> > * There is an unstable and a stable branch in the super/master
> repository.
> > * The submodules might be at different revisions in the branches.
> > * You are at some place without internet connection ;)
> >
> > With this patch it is now possible to change branches and update
> > the submodules to be at the recorded revision without online access.
>
> How is this better than "cd submodule/path && git checkout whatever"?
It is better if you have a complex setup recorded in the master repository.
If my co-worker commited his newest revisions for the "stable" branch, I
might not know which of his revisions I need to checkout.
> > Another advantage is that with -N the update operation is faster,
> > because fetch is checking for new updates even if there was no
> > fetch/pull on the super/master repository since the last update.
>
> Do we know this is common enough to deserve a shortopt -N?
I don't think so, gonna resend later.
> The logic of the patch itself looks sane to me.
Nice.
Best Wishes,
Fabian
next prev parent reply other threads:[~2009-02-07 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 22:18 [PATCH] submodule: add --no-fetch parameter to update command Fabian Franz
2009-02-06 18:01 ` Lars Hjemli
2009-02-07 15:44 ` Fabian Franz [this message]
2009-02-07 8:44 ` 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=20090207154425.325390@gmx.net \
--to=fabianfranz@gmx.de \
--cc=git@vger.kernel.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).