git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Mateusz Loskot <mateusz@loskot.net>
To: git@vger.kernel.org
Subject: "Submodule registered for path" output with config aliases mixed in
Date: Tue, 19 Feb 2019 17:51:05 +0100	[thread overview]
Message-ID: <CABUeae_N3NFXn-E1+LHORL3RDf5iTCFn=zyuOo3c2Aot2QF7pg@mail.gmail.com> (raw)

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] ?


[1] https://github.com/mloskot/wsl-config/tree/master/git

-- 
Best regards,
Mateusz Łoskot, http://mateusz.loskot.net

             reply	other threads:[~2019-02-19 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 16:51 Mateusz Loskot [this message]
2019-02-20 16:30 ` "Submodule registered for path" output with config aliases mixed in Mateusz Loskot
2019-02-21  2:18 ` brian m. carlson
2019-02-21  3:47   ` Duy Nguyen
2019-02-21  4:17     ` Jeff King
2019-02-21 10:53       ` Mateusz Loskot
2019-02-21 13:07         ` Jeff King
2019-02-21 20:01           ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABUeae_N3NFXn-E1+LHORL3RDf5iTCFn=zyuOo3c2Aot2QF7pg@mail.gmail.com' \
    --to=mateusz@loskot.net \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).