git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Zager <szager@google.com>
Cc: git@vger.kernel.org, Heiko Voigt <hvoigt@hvoigt.net>,
	Jens Lehmann <Jens.Lehmann@web.de>,
	Lars Hjemli <hjemli@gmail.com>
Subject: Re: submodule update --force
Date: Thu, 10 May 2012 07:58:09 -0700	[thread overview]
Message-ID: <7v8vh0ozge.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAHOQ7J_6+sfU6egjvVSPj-FAS6zjSUT=a057=kz_wYbogHLMMA@mail.gmail.com> (Stefan Zager's message of "Thu, 10 May 2012 00:20:19 -0700")

Stefan Zager <szager@google.com> writes:

> ...  To my mind, any
> `git submodule` command should *always* run on the first level of
> submodules.  If you're going to specify --no-recurse, then why are you
> running `git submodule` at all?  I think 'recursion' only applies to
> moving beyond the first level of submodules.

Very true.

Submodule folks, any opinion on the Stefan's approach?

  reply	other threads:[~2012-05-10 14:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHOQ7J8r4m2rz57BdkM9CADHdHE1yDFwExyF87u=DCEXjqzcqw@mail.gmail.com>
2012-05-09 23:55 ` submodule update --force Stefan Zager
2012-05-10  5:47   ` Junio C Hamano
2012-05-10  6:18     ` Junio C Hamano
2012-05-10  7:20       ` Stefan Zager
2012-05-10 14:58         ` Junio C Hamano [this message]
2012-05-10 18:57           ` Heiko Voigt
2012-05-11 20:56             ` Phil Hord
2012-05-14 16:52               ` Heiko Voigt
2012-05-14 17:17                 ` Stefan Zager
2012-05-14 19:18                   ` Heiko Voigt
2012-05-14 19:29                     ` Stefan Zager
2012-05-14 20:16                       ` Heiko Voigt

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=7v8vh0ozge.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=hvoigt@hvoigt.net \
    --cc=szager@google.com \
    /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).