git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Voigt <hvoigt@hvoigt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jens Lehmann <jens.lehmann@web.de>
Subject: Re: Re: [PATCH 0/2] Add an update=none option for 'loose' submodules
Date: Mon, 22 Aug 2011 22:00:52 +0200	[thread overview]
Message-ID: <20110822200052.GC11745@sandbox-rc> (raw)
In-Reply-To: <7vy5yujtr2.fsf@alter.siamese.dyndns.org>

Hi,

On Mon, Aug 15, 2011 at 01:37:53PM -0700, Junio C Hamano wrote:
> Heiko Voigt <hvoigt@hvoigt.net> writes:
> 
> > On Thu, Aug 11, 2011 at 11:28:31AM -0700, Junio C Hamano wrote:
> >> Heiko Voigt <hvoigt@hvoigt.net> writes:
> >> > We have been talking about loose submodules for some time:
> >> 
> >> Also before introducing a new terminology "loose submodule", please define
> >> it somewhere. It feels confusing to me that a normal submodule, which
> >> shouldn't be auto-cloned nor auto-updated without "submodule init", needs
> >> to be called by a name other than simply a "submodule" but with an
> >> adjuctive "loose submodule".
> >
> > Thats why I avoided talking about it in the docs. For the commit message
> > I thought it would be kind of intuitive but I can update the commit
> > message so that it becomes more clear.
> 
> That sounds like a good thing to do.

I discovered that I only talked in the cover letter about the term
'loose'. Since that will not go into any commit I guess we can keep the
series this way?

Cheers Heiko

  reply	other threads:[~2011-08-22 20:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 17:51 [PATCH 0/2] Add an update=none option for 'loose' submodules Heiko Voigt
2011-08-11 17:51 ` [PATCH 1/2] submodule: move update configuration variable further up Heiko Voigt
2011-08-11 17:51 ` [PATCH 2/2] add update 'none' flag to disable update of submodule by default Heiko Voigt
2011-08-11 18:28 ` [PATCH 0/2] Add an update=none option for 'loose' submodules Junio C Hamano
2011-08-11 20:00   ` Heiko Voigt
2011-08-15 20:37     ` Junio C Hamano
2011-08-22 20:00       ` Heiko Voigt [this message]
2011-08-22 22:42         ` Junio C Hamano
2011-08-23 19:43           ` Heiko Voigt
2011-08-23 20:18             ` Jens Lehmann
2011-08-23 21:46               ` Junio C Hamano
2011-08-24 19:30                 ` Heiko Voigt
2011-08-26  6:27                   ` Junio C Hamano
2011-08-26 16:14                     ` Jens Lehmann
2011-08-24 20:38               ` 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=20110822200052.GC11745@sandbox-rc \
    --to=hvoigt@hvoigt.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jens.lehmann@web.de \
    /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).