From: Lars Schneider <larsxschneider@gmail.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git-for-windows <git-for-windows@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>,
me@ttaylorr.com
Subject: Re: [git-for-windows] [ANNOUNCE] Prerelease: Git for Windows v2.11.0-rc0
Date: Wed, 9 Nov 2016 23:12:05 +0100 [thread overview]
Message-ID: <B2BEB5B4-5CF0-4CD7-A8E2-50D51E00D2FF@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611051025030.3108@virtualbox>
On 05 Nov 2016, at 10:50, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:
> Dear Git users,
>
> I finally got around to rebase the Windows-specific patches (which seem to
> not make it upstream as fast as we get new ones) on top of upstream Git
> v2.11.0-rc0, and to bundle installers, portable Git and MinGit [*1*]:
>
> https://github.com/git-for-windows/git/releases/tag/v2.11.0-rc0.windows.1
I tested a new feature in 2.11 on Windows today and it failed. After some
confusion I realized that the feature is not on your 2.11 branch. Consider this:
My last patch on your 2.11 branch is
"pack-protocol: fix maximum pkt-line size" (7841c4):
https://github.com/git-for-windows/git/commits/v2.11.0-rc0.windows.1?author=larsxschneider
My last patch on the Git 2.11 branch is
"read-cache: make sure file handles are not inherited by child processes" (a0a6cb):
https://github.com/git/git/commits/v2.11.0-rc0?author=larsxschneider
Do you have a clue what is going on?
Thanks,
Lars
next prev parent reply other threads:[~2016-11-09 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 9:50 [ANNOUNCE] Prerelease: Git for Windows v2.11.0-rc0 Johannes Schindelin
2016-11-09 22:12 ` Lars Schneider [this message]
2016-11-10 21:39 ` [git-for-windows] " Johannes Schindelin
2016-11-11 8:28 ` Lars Schneider
2016-11-11 18:37 ` Johannes Schindelin
2016-11-10 8:12 ` stefan.naewe
2016-11-11 16:54 ` Johannes Schindelin
2016-11-11 18:33 ` Johannes Schindelin
2016-11-14 8:04 ` stefan.naewe
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=B2BEB5B4-5CF0-4CD7-A8E2-50D51E00D2FF@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=me@ttaylorr.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).