From: grizzly.nyo@gmail.com
To: msysgit@googlegroups.com
Cc: git@vger.kernel.org
Subject: Re: Git for Windows 1.8.5.2 (preview)
Date: Wed, 22 Jan 2014 06:58:26 -0800 (PST) [thread overview]
Message-ID: <39bdacb2-8bda-4a70-ae12-f3ca6daec3ea@googlegroups.com> (raw)
In-Reply-To: <alpine.DEB.1.00.1312310043240.1191@s15462909.onlinehome-server.info>
[-- Attachment #1: Type: text/plain, Size: 2693 bytes --]
Hi All,
It would seem that the released binaries do not match the tag in github.
For example core.fscache is not listed in the documentation shipped with
msysGit-fullinstall-1.8.5.2-preview20131230.exe.
Another is git-1.8.5.2.msysgit.0\Documentation\technical\api-hashmap.txt
missing as well.
Was this intentional?
Thank you for all your hard work!
On Tuesday, December 31, 2013 1:57:20 AM UTC+2, Johannes Schindelin wrote:
>
> Dear fans of Git,
>
> this mail brings to you the good news that Git for Windows is available in
> a new version: 1.8.5.2-preview20131230
>
> Many, many thanks go to the tireless developers working on this
> particularly hard port of Git.
>
> Changes since Git-1.8.4-preview20130916
>
> New Features
>
> - Comes with Git 1.8.5.2 plus Windows-specific patches.
>
> - Windows-specific patches are now grouped into pseudo-branches which
> should make future development more robust despite the fact that we have
> had less than stellar success getting the Windows-specific patches
> accepted
> by upstream git.git.
>
> - Works around more path length limitations (pull request #86)
>
> - Has an optional stat() cache toggled via core.fscache (pull request
> #107)
>
> Bugfixes
>
> - Lots of installer fixes
>
> - git-cmd: Handle home directory on a different drive correctly (pull
> request #146)
>
> - git-cmd: add a helper to work with the ssh agent (pull request #135)
>
> - Git-Cheetah: prevent duplicate menu entries (pull request #7)
>
> - No longer replaces dos2unix with hd2u (a more powerful, but slightly
> incompatible version of dos2unix)
>
> In keeping with the fine tradition of making a release on the eve of a
> holiday, and immediately going on vacation, it is my pleasure to wish you
> all a happy new year,
> Johannes
>
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[-- Attachment #2: Type: text/html, Size: 3356 bytes --]
prev parent reply other threads:[~2014-01-22 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 23:57 Git for Windows 1.8.5.2 (preview) Johannes Schindelin
2014-01-22 14:58 ` grizzly.nyo [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39bdacb2-8bda-4a70-ae12-f3ca6daec3ea@googlegroups.com \
--to=grizzly.nyo@gmail.com \
--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.
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 NNTP newsgroup(s).