From: Karsten Blees <karsten.blees@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2014, #04; Tue, 22)
Date: Wed, 23 Jul 2014 16:17:56 +0200 [thread overview]
Message-ID: <53CFC414.1010601@gmail.com> (raw)
In-Reply-To: <xmqq4my9f4qw.fsf@gitster.dls.corp.google.com>
Am 22.07.2014 23:44, schrieb Junio C Hamano:
>
> * sk/mingw-uni-fix-more (2014-07-21) 14 commits
> - Win32: enable color output in Windows cmd.exe
> - Win32: patch Windows environment on startup
> - Win32: keep the environment sorted
> - Win32: use low-level memory allocation during initialization
> - Win32: reduce environment array reallocations
> - Win32: don't copy the environment twice when spawning child processes
> - Win32: factor out environment block creation
> - Win32: unify environment function names
> - Win32: unify environment case-sensitivity
> - Win32: fix environment memory leaks
> - Win32: Unicode environment (incoming)
> - Win32: Unicode environment (outgoing)
> - Revert "Windows: teach getenv to do a case-sensitive search"
> - tests: do not pass iso8859-1 encoded parameter
>
> Most of these are battle-tested in msysgit and are needed to
> complete what has been merged to 'master' already.
>
> A fix has been squashed into "Unicode environ (outgoing)"; is this
> now ready to go?
>
>
> * sk/mingw-tests-workaround (2014-07-21) 6 commits
> - t800[12]: work around MSys limitation
> - t9902: mingw-specific fix for gitfile link files
> - t4210: skip command-line encoding tests on mingw
> - MinGW: disable legacy encoding tests
> - t0110/MinGW: skip tests that pass arbitrary bytes on the command line
> - MinGW: Skip test redirecting to fd 4
> (this branch is used by jc/not-mingw-cygwin.)
>
> Make tests pass on msysgit by mostly disabling ones that are
> infeasible on that platform.
>
> The t0110 one has been replaced; is this now ready to go?
>
Yes, I think both series are ready.
Compiles with msysgit and MSVC (with NO_CURL=1).
With the version in pu, three tests fail. t7001 is fixed with a newer 'cp'.
The other two are unrelated (introduced by nd/multiple-work-trees topic).
* t1501-worktree: failed 1
As of 5bbcb072 "setup.c: support multi-checkout repo setup"
Using $TRASH_DIRECTORY doesn't work on Windows.
* t2026-prune-linked-checkouts: failed 1
As of 404a45f1 "prune: strategies for linked checkouts"
Dito.
* t7001-mv: failed 6
'cp -P' doesn't work due to outdated cp.exe.
next prev parent reply other threads:[~2014-07-23 14:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 21:44 What's cooking in git.git (Jul 2014, #04; Tue, 22) Junio C Hamano
2014-07-23 6:56 ` Philip Oakley
2014-07-23 18:10 ` Junio C Hamano
2014-07-24 22:37 ` Philip Oakley
2014-07-24 22:45 ` Junio C Hamano
2014-07-25 22:08 ` Junio C Hamano
2014-07-28 22:12 ` Philip Oakley
2014-07-30 17:13 ` Everyday contents (was Re: What's cooking in git.git (Jul 2014, #04; Tue, 22)) Junio C Hamano
2014-08-05 20:26 ` Junio C Hamano
2014-08-05 21:00 ` Philip Oakley
2014-08-02 17:28 ` Everday contents (was part of " Philip Oakley
2014-08-03 17:29 ` Everday contents Junio C Hamano
2014-08-03 18:41 ` Philip Oakley
2014-08-04 17:00 ` Junio C Hamano
2014-07-23 14:17 ` Karsten Blees [this message]
2014-07-23 18:24 ` What's cooking in git.git (Jul 2014, #04; Tue, 22) Junio C Hamano
2014-07-25 12:30 ` Duy Nguyen
2014-07-29 19:43 ` [RFC/PATCH] Windows tests: let $TRASH_DIRECTORY point to native Windows path Karsten Blees
2014-08-27 13:08 ` Duy Nguyen
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=53CFC414.1010601@gmail.com \
--to=karsten.blees@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).