git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jens Lehmann" <Jens.Lehmann@web.de>
To: "Lukasz Palczewski" <l.palczewski@prevac.pl>
Cc: git@vger.kernel.org, "Jonathan Nieder" <jrnieder@gmail.com>
Subject: Re: Restart submodule update --recursive
Date: Sat, 30 Oct 2010 09:17:55 +0200 (CEST)	[thread overview]
Message-ID: <212962199.646095.1288423075790.JavaMail.fmail@mwmweb046> (raw)
In-Reply-To: <4CCAB20A.1000408@prevac.pl>

>Let me know if this change will be in next version of git.

Sorry I'm coming late into this thread,but I'm still traveling.

Lukasz, maybe you could wait until I finish the recursive checkout I am
currently working on? Because then there will be no need to run
"git submodule update" anymore, but "git checkout" will update
submodules recursively too. And it will only fail if the checkout would
overwrite your local modifications, not just because the submodule is
modified in some way, and in this case it won't start at all instead of stopping
somewhere in between (you can test that new behavior by checking
out the branch "enhance_git_for_submodules" of my github repo:
http://github.com/jlehmann/git-submod-enhancements ).

Would that solve your problem?

  parent reply	other threads:[~2010-10-30  7:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28  7:25 Restart submodule update --recursive Lukasz Palczewski
2010-10-28 10:35 ` Johan Herland
2010-10-29  7:28   ` Lukasz Palczewski
2010-10-28 18:15 ` Jonathan Nieder
2010-10-29  7:17   ` Lukasz Palczewski
2010-10-29  9:12     ` Jonathan Nieder
2010-10-29 11:37       ` Lukasz Palczewski
2010-10-29 16:40         ` Jonathan Nieder
2010-10-30  7:17         ` Jens Lehmann [this message]
2010-11-02  8:18           ` Lukasz Palczewski
2010-11-02 11:08             ` Jens Lehmann

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=212962199.646095.1288423075790.JavaMail.fmail@mwmweb046 \
    --to=jens.lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=l.palczewski@prevac.pl \
    /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).