threads / discuss / 19725

Git for Windows 1.6.3.2

Subject: Git for Windows 1.6.3.2

## tl;dr

13 messages between Jun 7, 2009 and Jun 9, 2009.

replies: 12people: 5as markdown or json

Johannes Schindelin· Jun 7, 2009, 14:33 UTC · lore

Hi,

this mail informs you that Git for Windows 1.6.3.2 is out. Soon is the time that we switch to git.git's master.

Git Release Notes (Git-1.6.3.2-preview20090607) Last update: 07 June 2009

Introduction These release notes describe issues specific to the Windows release.

General release notes covering the history of the core git commands are included in the subdirectory doc/git/html of the installation directory. Look for files starting with RelNotes.

Known issues
- Some commands are not yet supported on Windows and excluded from the 
  installation; namely: git archimport, git cvsexportcommit, git 
  cvsimport, git cvsserver, git instaweb, git send-email, git shell.
- The Logitec QuickCam software can cause spurious crashes. See "Why does 
  make often crash creating a sh.exe.stackdump file when I try to compile 
  my source code?" on the MinGW Wiki 
  (http://www.mingw.org/wiki/Environment_issues)
- The Quick Launch icon will only be installed for the user running setup 
  (typically the Administrator). This is a technical restriction and will 
  not change.
- Git Bash launched through the Explorer shell extension does not have the 
  git icon in its taskbar. This is a technical restriction and will not 
  change.
- git send-mail does not work properly (Issue 27).
- curl uses $HOME/_netrc instead of $HOME/.netrc.
- If you want to specify a different location for --upload-pack, you have 
  to start the absolute path with two slashes. Otherwise MSys will mangle 
  the path.
- git and bash have serious problems with non-ASCII file names (Issue 80, 
  159).
- If configured to use plink, you will have to connect with putty first.
- MinGW does not support IPv6 yet (Issue 182). 
- When run from cmd.exe instead of Git Bash, some characters seem to be 
  "swallowed" from Git's output (Issue 192).
- There are a spurious write errors during rebase (Issue 200) that seem 
  not to be reproducible on most computers.
- As merge tools are executed using the MSys bash, options starting with 
  "/" need to be handled specially: MSys would interpret that as a POSIX 
  path, so you need to double the slash (Issue 226).  Example: instead of 
  "/base", say "//base".
- Also, extra care has to be paid to pass Windows programs Windows paths, 
  as they have no clue about MSys style POSIX paths -- You can use 
  something like $(cmd //c echo "$POSIXPATH").

Changes since Git-1.6.3-preview20090507

New Features
- Comes with official git 1.6.3.2.
- Uses TortoisePlink instead of Plink if available.

Bugfixes
- Plink errors out rather than hanging when the user needs to accept a 
  host key first (Issue 96).
- The user home directory is inferred from $HOMEDRIVE\$HOMEPATH instead of 
  $HOME (Issue 108).
- The environment setting $CYGWIN=tty is ignored (Issues 138, 248 and 
  251).
- The "ls" command shows non-ASCII filenames correctly now (Issue 188).
- Adds more syntax files for vi (Issue 250).
- $HOME/.bashrc is included last from /etc/profile, allowing .bashrc to 
  override all settings in /etc/profile (Issue 255).
- Completion is case-insensitive again (Issue 256).
- The "start" command can handle arguments with spaces now (Issue 258).
- For some Git commands (such as "git commit"), vi no longer "restores" 
  the cursor position.

Ferry Huberts (Pelagic)· Jun 8, 2009, 10:01 UTC · re: Johannes Schindelin · lore

Re: Git for Windows 1.6.3.2

Hi,

I just installed it and it seems that ~ now points to /c ... which is odd and break stuff.

Is this expected or a bug? Or am I doing something wrong?

I installed default: using git bash, unix line endings, ssh, etc

-- 
Ferry Huberts



On Sun, June 7, 2009 16:33, Johannes Schindelin wrote:
> Hi,
>
> this mail informs you that Git for Windows 1.6.3.2 is out.  Soon is the
> time that we switch to git.git's master.
>
> Git Release Notes (Git-1.6.3.2-preview20090607)
> Last update: 07 June 2009
>
> Introduction
> These release notes describe issues specific to the Windows release.
>
> General release notes covering the history of the core git commands are
> included in the subdirectory doc/git/html of the installation directory.
> Look for files starting with RelNotes.
>
> Known issues
> - Some commands are not yet supported on Windows and excluded from the
>   installation; namely: git archimport, git cvsexportcommit, git
>   cvsimport, git cvsserver, git instaweb, git send-email, git shell.
> - The Logitec QuickCam software can cause spurious crashes. See "Why does
>   make often crash creating a sh.exe.stackdump file when I try to compile
>   my source code?" on the MinGW Wiki
>   (http://www.mingw.org/wiki/Environment_issues)
> - The Quick Launch icon will only be installed for the user running setup
>   (typically the Administrator). This is a technical restriction and will
>   not change.
> - Git Bash launched through the Explorer shell extension does not have the
>   git icon in its taskbar. This is a technical restriction and will not
>   change.
> - git send-mail does not work properly (Issue 27).
> - curl uses $HOME/_netrc instead of $HOME/.netrc.
> - If you want to specify a different location for --upload-pack, you have
>   to start the absolute path with two slashes. Otherwise MSys will mangle
>   the path.
> - git and bash have serious problems with non-ASCII file names (Issue 80,
>   159).
> - If configured to use plink, you will have to connect with putty first.
> - MinGW does not support IPv6 yet (Issue 182).
> - When run from cmd.exe instead of Git Bash, some characters seem to be
>   "swallowed" from Git's output (Issue 192).
> - There are a spurious write errors during rebase (Issue 200) that seem
>   not to be reproducible on most computers.
> - As merge tools are executed using the MSys bash, options starting with
>   "/" need to be handled specially: MSys would interpret that as a POSIX
>   path, so you need to double the slash (Issue 226).  Example: instead of
>   "/base", say "//base".
> - Also, extra care has to be paid to pass Windows programs Windows paths,
>   as they have no clue about MSys style POSIX paths -- You can use
>   something like $(cmd //c echo "$POSIXPATH").
>
> Changes since Git-1.6.3-preview20090507
>
> New Features
> - Comes with official git 1.6.3.2.
> - Uses TortoisePlink instead of Plink if available.
>
> Bugfixes
> - Plink errors out rather than hanging when the user needs to accept a
>   host key first (Issue 96).
> - The user home directory is inferred from $HOMEDRIVE\$HOMEPATH instead of
>   $HOME (Issue 108).
> - The environment setting $CYGWIN=tty is ignored (Issues 138, 248 and
>   251).
> - The "ls" command shows non-ASCII filenames correctly now (Issue 188).
> - Adds more syntax files for vi (Issue 250).
> - $HOME/.bashrc is included last from /etc/profile, allowing .bashrc to
>   override all settings in /etc/profile (Issue 255).
> - Completion is case-insensitive again (Issue 256).
> - The "start" command can handle arguments with spaces now (Issue 258).
> - For some Git commands (such as "git commit"), vi no longer "restores"
>   the cursor position.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Ferry Huberts· Jun 8, 2009, 10:43 UTC · re: Johannes Schindelin · lore

Re: Git for Windows 1.6.3.2

On Sun, June 7, 2009 16:33, Johannes Schindelin wrote:

Show 7 quoted lines

> Hi,
>
> this mail informs you that Git for Windows 1.6.3.2 is out.  Soon is the
> time that we switch to git.git's master.
>
> - The user home directory is inferred from $HOMEDRIVE\$HOMEPATH instead of
>   $HOME (Issue 108).

this does not work for me. win xp sp3, 32bits

with this patch it is fixed/reverted:

--- Program Files/Git/etc/profile.org 2009-06-08 12:31:29.968750000 +0200 +++ Program Files/Git/etc/profile 2009-06-08 12:31:16.718750000 +0200

@@ -29,7 +29,7 @@

 # Set up USER's home directory
 if [ -z "$HOME" -o ! -d "$HOME" ]; then
-  HOME="$HOMEDRIVE$HOMEPATH"
+  HOME="$USERPROFILE"
 fi

 if [ ! -d "$HOME" ]; then

Sverre Rabbelier· Jun 8, 2009, 10:51 UTC · re: Ferry Huberts · lore

Re: Git for Windows 1.6.3.2

Heya,

On Mon, Jun 8, 2009 at 12:43, Ferry Huberts<ferry.huberts@pelagic.nl> wrote:

> this does not work for me.

Perhaps you want to define 'does not work'

> with this patch it is fixed/reverted:

I doubt simply reverting the 'fix' is going to be a good idea, methinks the original fix was done for a reason, no?

-- 
Cheers,

Sverre Rabbelier

Johannes Schindelin· Jun 8, 2009, 10:58 UTC · re: Sverre Rabbelier · lore

Re: Git for Windows 1.6.3.2

Hi,

On Mon, 8 Jun 2009, Sverre Rabbelier wrote:

Show 5 quoted lines

> On Mon, Jun 8, 2009 at 12:43, Ferry Huberts<ferry.huberts@pelagic.nl> 
> wrote:
> > this does not work for me.
> 
> Perhaps you want to define 'does not work'

Well, it is clear, no?  It "does not work".

:-)

> > with this patch it is fixed/reverted:
> 
> I doubt simply reverting the 'fix' is going to be a good idea, methinks 
> the original fix was done for a reason, no?

The original fix was indeed done for a reason.

My best guess (as I said in another email on the msysgit list today, where Ferry probably did not expect helpful information): msys-1.0.dll was not properly updated.

I worked on a check for this some time ago, but I forgot to finish and include it in our official 'devel'.

Ciao, Dscho

Ferry Huberts· Jun 8, 2009, 11:05 UTC · re: Johannes Schindelin · lore

Re: Git for Windows 1.6.3.2

Show 5 quoted lines

> The original fix was indeed done for a reason.
>
> My best guess (as I said in another email on the msysgit list today, where
> Ferry probably did not expect helpful information): msys-1.0.dll was not
> properly updated.

sorry for that, I am subscribed to git.devel only. probably should have checked the msysgit list

>
> I worked on a check for this some time ago, but I forgot to finish and
> include it in our official 'devel'.

does this mean that we can expect a '-2' msysgit release soon?

Johannes Schindelin· Jun 8, 2009, 12:03 UTC · re: Ferry Huberts · lore

Re: Git for Windows 1.6.3.2

Hi,

On Mon, 8 Jun 2009, Ferry Huberts wrote:

Show 13 quoted lines

> > The original fix was indeed done for a reason.
> >
> > My best guess (as I said in another email on the msysgit list today, 
> > where Ferry probably did not expect helpful information): msys-1.0.dll 
> > was not properly updated.
> 
> sorry for that, I am subscribed to git.devel only. probably should have 
> checked the msysgit list
> 
> > I worked on a check for this some time ago, but I forgot to finish and 
> > include it in our official 'devel'.
> 
> does this mean that we can expect a '-2' msysgit release soon?

No.

Ciao, Dscho

Johannes Schindelin· Jun 9, 2009, 13:58 UTC · re: Johannes Schindelin · lore

Re: Git for Windows 1.6.3.2

Hi,

On Mon, 8 Jun 2009, Johannes Schindelin wrote:

Show 17 quoted lines

> On Mon, 8 Jun 2009, Ferry Huberts wrote:
> 
> > > The original fix was indeed done for a reason.
> > >
> > > My best guess (as I said in another email on the msysgit list today, 
> > > where Ferry probably did not expect helpful information): msys-1.0.dll 
> > > was not properly updated.
> > 
> > sorry for that, I am subscribed to git.devel only. probably should have 
> > checked the msysgit list
> > 
> > > I worked on a check for this some time ago, but I forgot to finish and 
> > > include it in our official 'devel'.
> > 
> > does this mean that we can expect a '-2' msysgit release soon?
> 
> No.

Just to clarify: there is no -2 release, because it is a new day. And no, I did not like the feeling that you "expect" me to do the work at all.

An example I positively _like_ is Tom Koelman, who tried the net installer (pointing out an issue I had not encountered before) and built his own Git installer, the better to help me fix bugs in the future.

Ciao, Dscho

Ferry Huberts· Jun 9, 2009, 15:15 UTC · re: Johannes Schindelin · lore

Re: Git for Windows 1.6.3.2

Show 8 quoted lines

>
> Just to clarify: there is no -2 release, because it is a new day.  And no,
> I did not like the feeling that you "expect" me to do the work at all.
>
> An example I positively _like_ is Tom Koelman, who tried the net installer
> (pointing out an issue I had not encountered before) and built his own Git
> installer, the better to help me fix bugs in the future.
>

wow

sorry I rubbed you the wrong way. that was by no means my intention and I'm surprised that you took it that way.

AFAIK I was being polite and positive. I've sent you a patch by which I made it work. I just asked whether there would be a new release _without_ expecting anything.

besides, for me the -2 question was totally valid in the light of a broken installer and what you did the last time that happened

I have no time to build my own installer. I guess we're both swamped by work...

Dirk Süsserott· Jun 9, 2009, 19:18 UTC · re: Johannes Schindelin · lore

Re: Git for Windows 1.6.3.2

Am 08.06.2009 12:58 schrieb Johannes Schindelin:

Show 5 quoted lines

> 
> My best guess (as I said in another email on the msysgit list today, where 
> Ferry probably did not expect helpful information): msys-1.0.dll was not 
> properly updated.
>

Hi Dscho,

I *knew* there must be a mailing list for msysgit only, but I couldn't figure out where. Can you please give me a pointer where to register? I'm registered with Junios list, but as a windows user I'd like to read and participate with your's as well.

Cheers, Dirk

Sverre Rabbelier· Jun 9, 2009, 20:34 UTC · re: Dirk Süsserott · lore

Re: Git for Windows 1.6.3.2

Heya,

2009/6/9 Dirk Süsserott <newsletter@dirk.my1.cc>:

> I *knew* there must be a mailing list for msysgit only, but I couldn't
> figure out where. Can you please give me a pointer where to register? I'm
> registered with Junios list, but as a windows user I'd like to read and
> participate with your's as well.

Try Google groups [0].

[0] http://groups.google.com/group/msysgit

-- 
Cheers,

Sverre Rabbelier

Ferry Huberts· Jun 8, 2009, 11:02 UTC · re: Sverre Rabbelier · lore

Re: Git for Windows 1.6.3.2

On Mon, June 8, 2009 12:51, Sverre Rabbelier wrote:

Show 7 quoted lines

> Heya,
>
> On Mon, Jun 8, 2009 at 12:43, Ferry Huberts<ferry.huberts@pelagic.nl> wrote:
>> this does not work for me.
>
> Perhaps you want to define 'does not work'
>

sure:

This is what cmd.exe says: HOMEDRIVE=C: HOMEPATH=\Documents and Settings\hubertsf

This is what Git bash says: HOMEDRIVE=C: HOMEPATH='\'

Appearently $HOMEPATH is somehow different. Note that I do have Cygwin installed, but as far as i can see Cygwin does not cause $HOMEPATH to be set to /

Lee Henson· Jun 8, 2009, 12:58 UTC · re: Johannes Schindelin · lore

Re: Git for Windows 1.6.3.2

Many thanks, Johannes.

2009/6/7 Johannes Schindelin <Johannes.Schindelin@gmx.de>

Show 75 quoted lines

>
> Hi,
>
> this mail informs you that Git for Windows 1.6.3.2 is out.  Soon is the
> time that we switch to git.git's master.
>
> Git Release Notes (Git-1.6.3.2-preview20090607)
> Last update: 07 June 2009
>
> Introduction
> These release notes describe issues specific to the Windows release.
>
> General release notes covering the history of the core git commands are
> included in the subdirectory doc/git/html of the installation directory.
> Look for files starting with RelNotes.
>
> Known issues
> - Some commands are not yet supported on Windows and excluded from the
>  installation; namely: git archimport, git cvsexportcommit, git
>  cvsimport, git cvsserver, git instaweb, git send-email, git shell.
> - The Logitec QuickCam software can cause spurious crashes. See "Why does
>  make often crash creating a sh.exe.stackdump file when I try to compile
>  my source code?" on the MinGW Wiki
>  (http://www.mingw.org/wiki/Environment_issues)
> - The Quick Launch icon will only be installed for the user running setup
>  (typically the Administrator). This is a technical restriction and will
>  not change.
> - Git Bash launched through the Explorer shell extension does not have the
>  git icon in its taskbar. This is a technical restriction and will not
>  change.
> - git send-mail does not work properly (Issue 27).
> - curl uses $HOME/_netrc instead of $HOME/.netrc.
> - If you want to specify a different location for --upload-pack, you have
>  to start the absolute path with two slashes. Otherwise MSys will mangle
>  the path.
> - git and bash have serious problems with non-ASCII file names (Issue 80,
>  159).
> - If configured to use plink, you will have to connect with putty first.
> - MinGW does not support IPv6 yet (Issue 182).
> - When run from cmd.exe instead of Git Bash, some characters seem to be
>  "swallowed" from Git's output (Issue 192).
> - There are a spurious write errors during rebase (Issue 200) that seem
>  not to be reproducible on most computers.
> - As merge tools are executed using the MSys bash, options starting with
>  "/" need to be handled specially: MSys would interpret that as a POSIX
>  path, so you need to double the slash (Issue 226).  Example: instead of
>  "/base", say "//base".
> - Also, extra care has to be paid to pass Windows programs Windows paths,
>  as they have no clue about MSys style POSIX paths -- You can use
>  something like $(cmd //c echo "$POSIXPATH").
>
> Changes since Git-1.6.3-preview20090507
>
> New Features
> - Comes with official git 1.6.3.2.
> - Uses TortoisePlink instead of Plink if available.
>
> Bugfixes
> - Plink errors out rather than hanging when the user needs to accept a
>  host key first (Issue 96).
> - The user home directory is inferred from $HOMEDRIVE\$HOMEPATH instead of
>  $HOME (Issue 108).
> - The environment setting $CYGWIN=tty is ignored (Issues 138, 248 and
>  251).
> - The "ls" command shows non-ASCII filenames correctly now (Issue 188).
> - Adds more syntax files for vi (Issue 250).
> - $HOME/.bashrc is included last from /etc/profile, allowing .bashrc to
>  override all settings in /etc/profile (Issue 255).
> - Completion is case-insensitive again (Issue 256).
> - The "start" command can handle arguments with spaces now (Issue 258).
> - For some Git commands (such as "git commit"), vi no longer "restores"
>  the cursor position.
>
>
>