From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Sun, 18 Jul 2010 18:11:30 GMT
Subject: Re: Challenge with Git-Bash
Message-ID: <AANLkTinZCKIDh8bJUVXceqNYD1qkmWZ1fO67t0XJI5Uo@mail.gmail.com>
In-Reply-To: <008a01cb26a4$4313e360$c93baa20$@gmx.net>

On Sun, Jul 18, 2010 at 18:08, Rainer Lauer <lauerr@gmx.net> wrote:
> Hi Jonathan,
> thanks for this hint. Now it is working on the base of environment variables.
>
> In order of automatically setting up my projects I'd like to use the configuration file for preparing  CVS-work instead introducing environment variables.
> Unfortunately, I'm facing another problem.
> Following commands don't modify .git/config coming along with my project(s).
> git config user.name="Rainer Lauer"
> git config user.email="Rainer.Lauer@gmx.net"
> git config core.editor="c:/Program Files/SlickEditV14.0.2/win/vs.exe"
> The file seems to stay in initial revision as created with the command git init.
>
> Where is following information stored? Command:  git config --global user.name="Rainer Lauer". Did I get the documentation right that this is a definition for all projects?

If you're asking why your .git/config file isn't being carried over
when you clone the repository that's because it's not supposed to, Git
doesn't work like that.