From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Mika Vesalainen <Mika.Vesalainen@u-blox.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Using Environment variable GIT_CONFIG does not work as expected
Date: Mon, 30 Jul 2018 15:07:57 +0200 [thread overview]
Message-ID: <20180730130757.22205-1-szeder.dev@gmail.com> (raw)
In-Reply-To: <LNXP265MB0892616339D20CA9B10D6A31D42F0@LNXP265MB0892.GBRP265.PROD.OUTLOOK.COM>
> I have a shared linux account which is used by multiple developers.
> But I would like to have git commit history configured so that I can
> see who made a change to common repository (so that author of the
> commit would be correct person, not shared user). There are reasons
> why developers cannot clone this environment to their own accounts.
>
> So I don't have ~/.gitconfig in place for the shared user, and when
> developer log in I enforce them to configure git for them first. They
> must "export GIT_CONFIG=my_specific_gitconfig".
> When this is done, "git config -l" will show correctly the user.name,
> user.email and other parameters which are set in
> "my_specific_gitconfig".
>
> However, if user tries now to create a commit the git blames:
> *** Please tell me who you are.
> and so on...
>
> But running "git config -l" shows that 'user.name' and 'user.email'
> are properly configured.
> Do I need to configure something more in order to get this GIT_CONFIG
> environment variable working. I'm working in Debian Linux environment.
I think it's working as intended, because GIT_CONFIG is only supposed
to affect 'git config' and is only documented in the git-config(1) man
page. Perhaps the wording could be improved to be more explicit about
this.
Note that more general environment variables affecting more git
commands are documented in git(1), and GIT_CONFIG is not mentioned
there.
Try setting and exporting the environment variables GIT_AUTHOR_NAME,
GIT_AUTHOR_EMAIL, GIT_COMMITTER_NAME, and GIT_COMMITTER_EMAIL instead.
>
> I have tested this with git versions: 2.1.4, 2.11.0 and
> 2.18.0.321.gffc6fa0
prev parent reply other threads:[~2018-07-30 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 8:58 Using Environment variable GIT_CONFIG does not work as expected Mika Vesalainen
2018-07-30 13:07 ` SZEDER Gábor [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
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=20180730130757.22205-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=Mika.Vesalainen@u-blox.com \
--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).