From: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: Git for Windows 1.6.3.2
Date: Mon, 8 Jun 2009 12:01:32 +0200 (CEST) [thread overview]
Message-ID: <13638.77.61.241.211.1244455293.squirrel@hupie.xs4all.nl> (raw)
In-Reply-To: <alpine.DEB.1.00.0906071629460.26154@pacific.mpi-cbg.de>
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
>
next prev parent reply other threads:[~2009-06-08 10:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 14:33 Git for Windows 1.6.3.2 Johannes Schindelin
2009-06-08 10:01 ` Ferry Huberts (Pelagic) [this message]
2009-06-08 10:43 ` Ferry Huberts
2009-06-08 10:51 ` Sverre Rabbelier
2009-06-08 10:58 ` Johannes Schindelin
2009-06-08 11:05 ` Ferry Huberts
2009-06-08 12:03 ` Johannes Schindelin
2009-06-09 13:58 ` Johannes Schindelin
2009-06-09 15:15 ` Ferry Huberts
2009-06-09 19:18 ` Dirk Süsserott
2009-06-09 20:34 ` Sverre Rabbelier
2009-06-08 11:02 ` Ferry Huberts
2009-06-08 12:58 ` Lee Henson
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=13638.77.61.241.211.1244455293.squirrel@hupie.xs4all.nl \
--to=ferry.huberts@pelagic.nl \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
/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).