From: <stefan.naewe@atlas-elektronik•com>
To: <git@vger•kernel.org>
Subject: Fwd: Re: Git config not working correctly with included configurations
Date: Tue, 12 Apr 2016 13:58:20 +0200 [thread overview]
Message-ID: <570CE2DC.90602@atlas-elektronik.com> (raw)
In-Reply-To: <570CE289.2000808@atlas-elektronik.com>
Sorry, I thought this list has 'reply to all' set by default...
Stefan
-------- Weitergeleitete Nachricht --------
Betreff: Re: Git config not working correctly with included configurations
Datum: Tue, 12 Apr 2016 13:56:57 +0200
Von: Näwe, Stefan <stefan.naewe@atlas-elektronik•com>
An: Rudinei Goi Roecker <rudineigr@itflex•com.br>
Am 12.04.2016 um 13:25 schrieb Rudinei Goi Roecker:
> I'm having a problem with included configurations in ~/.gitconfig, when
> using this command:
>
> git config --global user.email
>
> It doesn't return anything, in commits it works as intended. The
> configuration looks like this:
>
> ~/.gitconfig
> [include]
> path = .gitconfig.user
Maybe you want to use
path = ~/.gitconfig.user
here.
> # ... more configurations
>
> ~/.gitconfig.user
> [user]
> name = My Full Name
> email = myemail@example•com
HTH,
Stefan
--
----------------------------------------------------------------
/dev/random says: CURSOR: What you become when your system crashes.
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9 9666 829B 49C5 9221 27AF
next parent reply other threads:[~2016-04-12 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <570CDB33.9020300@itflex.com.br>
[not found] ` <570CE289.2000808@atlas-elektronik.com>
2016-04-12 11:58 ` stefan.naewe [this message]
2016-04-12 12:13 ` Git config not working correctly with included configurations Rudinei Goi Roecker
2016-04-12 11:25 Rudinei Goi Roecker
2016-04-12 13:02 ` John Keeping
2016-04-12 15:50 ` Jeff King
2016-04-12 16:03 ` Rudinei Goi Roecker
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=570CE2DC.90602@atlas-elektronik.com \
--to=stefan.naewe@atlas-elektronik$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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