"Philip Oakley" Sent: Wednesday, November 12, 2014 9:07 PM
> What is the right way of updating the git version that msys.bat will
> use?
> ---
Some extra research...
>
> I installed my developer environment back when $ git --version => git
> version 1.7.9.GIT was young ;-).
>
> Thus when I (occasionally) use my C:\msysgit179\msys.bat, I'm still
> getting the now old v1.7.9. located at.
> $ which git
> /bin/git
This is the "Welcome to msysGit" window (with the cmd.exe icon) and its
root is at my "C:\msysgit179\" (determined by comparing an 'ls' command
with a windows explorer view)
>
> Normally I'm using git bash (separately installed) via my main
> explorer shortcut C:\WINDOWS\system32\cmd.exe /c ""C:\Program
> Files\Git\bin\sh.exe" --login -i", which is version
> 1.9.4-preview20140611, so is not usually a problem.
>
This is the "Welcome to Git (version 1.9.4-preview20140611)" window with
the Git red diamond graph icon, and its root is "C:\Documents and
Settings\Philip\" (same confirmation method).
So it looks like 'root' wanders between instances.
Is there a way to get (reliably?) the Windows path for root from within
the bash windows?
I'm not aware of one. (everyones focus apperas to be on making it look
like Linux and making Windows vanish ;-)
>
> However I'd like to see if I can update, in-place, my developer
> environment version of git (at /bin/git).
i.e that exe's in "C:\msysgit179\bin\git.exe"
>
>
> What is the right way of updating the git version that msys.bat will
> use?
>
> I have recompiled the latest version of msysgit (v1.9.4.msysgit.2) in
> line with
>
https://git.wiki.kernel.org/index.php/MSysGit:UpdatingMSysGit and
> 'make' appears to have run correctly, though I haven't run the tests.
Ran the tests overnight (This is on my XP netbook!), with only a few
fails (for me).
"These tests failed: t3301-notes t4036-format-patch-signer-mime
t3420-rebase-autostash t5801-remote-helpers t6006-rev-list-format
t3404-rebase-interactive t9200-git-cvsexportcommit
Unfinished tests: t1303-wacky-config t9300-fast-import"
I've not tried any debugging of those.
My short term goal is to:
ensure I have a clean machine with relatively new Git installs,
then actually debug the generation of the '.sln' file for use with
Visual Studio as an IDE
(£dayjob includes use of VS2008, hence a familiarity prefernce, rather
than using Notepad++)
I've got a few patches from last year for the generation of the .sln for
Git, but there are still a few nits.