git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: Jacob Keller <jacob.keller@gmail.com>,
	Stefan Beller <sbeller@google.com>,
	Git Users <git@vger.kernel.org>,
	Jens.Lehmann@web.de
Subject: Re: [RFC] How to pass Git config command line instructions to Submodule commands?
Date: Thu, 28 Apr 2016 09:40:47 -0400	[thread overview]
Message-ID: <20160428134047.GA25364@sigill.intra.peff.net> (raw)
In-Reply-To: <FF931AB2-2381-4DF9-AE28-CE30EEC5C352@gmail.com>

On Thu, Apr 28, 2016 at 02:05:20PM +0200, Lars Schneider wrote:

> I am no expert in the Submodule code but I think the cloning of
> the submodules is not yet guarded with sanitize_submodule_env [3].
> That means the submodule is cloned with the GIT_CONFIG_PARAMETERS
> of the super project. That might explain why t5550 passes as the 
> credential config is only used in that area.
> 
> The submodule checkout is guarded with sanitize_submodule_env
> and therefore my Git-LFS filter use case is affect.
> 
> Does this sound reasonable?

Yes, that's exactly what's going on. git-submodule.sh's code _is_
broken, which is what you're seeing. I've just posted a series to fix
this. I think it would be reasonable to add filter.* to the whitelist on
top of that series.

-Peff

      reply	other threads:[~2016-04-28 13:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 10:39 [RFC] How to pass Git config command line instructions to Submodule commands? Lars Schneider
2016-04-25 17:02 ` Stefan Beller
2016-04-25 20:59   ` Jacob Keller
2016-04-25 21:24     ` Jeff King
2016-04-25 21:27       ` Jeff King
2016-04-28 11:06       ` Lars Schneider
2016-04-28 11:25         ` Jeff King
2016-04-28 12:05           ` Jeff King
2016-04-28 12:17             ` Jeff King
2016-04-28 13:35               ` [PATCH 0/5] fixes for sanitized submodule config Jeff King
2016-04-28 13:36                 ` [PATCH 1/5] t5550: fix typo in $HTTPD_URL Jeff King
2016-04-28 15:24                   ` Jacob Keller
2016-04-28 15:25                     ` Jeff King
2016-04-28 15:26                       ` Jacob Keller
2016-04-28 13:37                 ` [PATCH 2/5] t5550: break submodule config test into multiple sub-tests Jeff King
2016-04-28 15:21                   ` Stefan Beller
2016-04-28 15:25                     ` Jeff King
2016-04-28 15:25                     ` Jacob Keller
2016-04-28 13:37                 ` [PATCH 3/5] submodule: export sanitized GIT_CONFIG_PARAMETERS Jeff King
2016-04-28 15:25                   ` Stefan Beller
2016-04-28 15:28                     ` Jeff King
2016-04-28 15:35                       ` Stefan Beller
2016-04-28 16:51                       ` Johannes Schindelin
2016-04-28 15:28                   ` Jacob Keller
2016-04-28 15:36                     ` Jeff King
2016-04-28 15:40                       ` Jacob Keller
2016-04-28 13:38                 ` [PATCH 4/5] submodule--helper: move config-sanitizing to submodule.c Jeff King
2016-04-28 15:30                   ` Stefan Beller
2016-04-28 15:37                     ` Jeff King
2016-04-28 16:28                   ` Lars Schneider
2016-04-28 13:39                 ` [PATCH 5/5] submodule: use prepare_submodule_repo_env consistently Jeff King
2016-04-28 14:02                 ` [PATCH 0/5] fixes for sanitized submodule config Johannes Schindelin
2016-04-28 15:56                   ` Stefan Beller
2016-04-28 16:03                     ` Jacob Keller
2016-04-28 12:05           ` [RFC] How to pass Git config command line instructions to Submodule commands? Lars Schneider
2016-04-28 13:40             ` Jeff King [this message]

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=20160428134047.GA25364@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=jacob.keller@gmail.com \
    --cc=larsxschneider@gmail.com \
    --cc=sbeller@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).