git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: "Submodule registered for path" output with config aliases mixed in

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Feb 21, 2019, 02:18 UTC
Message-ID
<20190221021825.GB488342@genre.crustytoothpaste.net>
In-Reply-To
<CABUeae_N3NFXn-E1+LHORL3RDf5iTCFn=zyuOo3c2Aot2QF7pg@mail.gmail.com>
On Tue, Feb 19, 2019 at 05:51:05PM +0100, Mateusz Loskot wrote:
Show 27 quoted lines
> Hi,
> 
> $ git version
> git version 2.20.1.windows.1
> 
> I'm running `git clone --recurse-submodules https://XXX`
> The command seems to run well and completes with success.
> 
> However, I noticed strange output from git:
> 
> ```
> Submodule 'Binary/A' (https://XXX) registered for path '!f() {
> ~/AppData/Local/Fork/Fork.exe $PWD; }; fBinary/A'
> Submodule 'Binary/B' (https://XXX) registered for path 'À   ♂♦Binary/Intergraph'
> Submodule 'Binary/C' (https://XXX) registered for path '!sh -c 'git
> log $1@{1}..$1@{0} $@'Binary/C'
> Submodule 'Binary/D' (https://XXX) registered for path 'ls-files -o -i
> --exclude-standardBinary/D'
> Submodule 'Binary/E' (https://XXX) registered for path
> 'mergetool.TortoiseGitMerge.trustexitcodeBinary/E'
> ```
> 
> I managed to identify where that garbage injections come from:
> from git aliases I've got configured [1]
> 
> Could anyone explain what is happening here?
> Is there anything wrong with my ~/.gitconfig [1] ?

I see the right behavior on my system (Debian amd64/sid) with 2.21.0.rc0.258.g878e2cd30e and with master. I've built with ASan and don't see any memory warnings on my system.

Does your .gitmodules file appear to be correct in the main repository when you clone, or does it contain unexpected entries?

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
Previous: Mateusz LoskotNext: Duy Nguyen
Message 3 of 8 in “"Submodule registered for path" output with config aliases mixed in”
  1. Mateusz LoskotFeb 19, 2019
  2. Mateusz LoskotFeb 20, 2019
  3. brian m. carlsonFeb 21, 2019
  4. Duy NguyenFeb 21, 2019
  5. Jeff KingFeb 21, 2019
  6. Mateusz LoskotFeb 21, 2019
  7. Jeff KingFeb 21, 2019
  8. Junio C HamanoFeb 21, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.