Re: [msysGit] error: could not commit config file U:\/.gitconfig

[Konstantin Khomoutov]

On Tue, 14 Aug 2012 08:42:00 -0700 (PDT)
Randy Bustamante <randymbu...@yahoo.com> wrote:

[...]
> error: could not commit config file U:\/.gitconfig
> while executing
> "exec {C:/Program Files (x86)/Git/libexec/git-core/git-config.exe}
> --global --add gui.recentrepo U:/testgit"
According to the git-config manual page, using the "--global"
command-line option forces this binary to use "~/.gitconfig" as the
configuration file to inspect/modify.
Since ~ on Windows is usually expanded from the HOMERRIVE + HOMEPATH or
USERPROFILE environment variables, I would spawn cmd.exe and inspect
all of them -- supposedly your user has something weird in them.
Compare them with the profiles where Git works OK.

[Randy Bustamante]

There was a difference but making the environment variables consistent did not resolve the issue.
Below is a copy of the working and failing environment variables:

Working:                                                   Failing:
BASH:                                                      BASH:
   HOMEPATH=\                                                   HOMEPATH=\
   HOME=/u                                                      HOME=/u
   HOMEDRIVE=U:                                                 HOMEDRIVE=U:
   HOMESHARE=\\dc1.flybackenergy.local\rbustamante$             HOMESHARE=\\dc1\bthurman$

   USERPROFILE=C:\Users\rbustamante.FLYBACKENERGY               USERPROFILE=C:\Users\bthurman 

DOS:                                                        DOS:
   HOMEDRIVE=U:                                                 HOMEDRIVE=U:
   HOMEPATH=\                                                   HOMEPATH=\
   HOMESHARE=\\dc1.flybackenergy.local\rbustamante$             HOMESHARE=\\dc1\bthurman$

   USERPROFILE=C:\Users\rbustamante.FLYBACKENERGY               USERPROFILE=C:\Users\bthurman

Notice that HOMESHARE and USERPROFILE were not using a domain qualified path in the failing case.  The environment variables were updated and the same error persists.

Any other suggestions on what I can look into?