git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stepan Kasal <kasal@ucw.cz>,
	Karsten Blees <karsten.blees@gmail.com>,
	 GIT Mailing-list <git@vger.kernel.org>,
	msysGit <msysgit@googlegroups.com>
Subject: Re: Re: [PATCH 0/7] Second part of msysgit/unicode
Date: Wed, 18 Jun 2014 23:35:12 +0200	[thread overview]
Message-ID: <53A20610.80500@kdbg.org> (raw)
In-Reply-To: <xmqq7g4ejf6y.fsf@gitster.dls.corp.google.com>

Am 18.06.2014 19:33, schrieb Junio C Hamano:
> In the meantime, are Windows folks happy with the four topics queued
> on 'pu' so far?  I would like to start moving them down to 'next'
> and to 'master' soonish.
> 
> They consist of these individual patches:
> 
>     $ git shortlog ^master \
>       sk/mingw-dirent \
>       sk/mingw-main \
>       sk/mingw-uni-console \
>       sk/mingw-unicode-spawn-args

Topic sk/test-cmp-bin revealed a new breakage in t5000-tar-tree,
specifically, the penultimate test "remote tar.gz is allowed by
default". I have yet to find out what it is (I suspect a LF-CRLF
conversion issue) and whether it is in connection with one of these topics.

I haven't had a chance to test the topics in the field. In particular, I
have a few files with Shift-JIS content (but ASCII file names), and I
would like to see how well I fare with the unicode topics in this situation.

-- Hannes

-- 
-- 
*** 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/d/optout.

      reply	other threads:[~2014-06-18 21:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  9:37 [PATCH 0/7] Second part of msysgit/unicode Stepan Kasal
2014-06-11  9:37 ` [PATCH 1/7] Let mingw_execve() return an int Stepan Kasal
2014-06-11  9:37 ` [PATCH 2/7] Win32: simplify internal mingw_spawn* APIs Stepan Kasal
2014-06-11  9:37 ` [PATCH 3/7] Win32: fix potential multi-threading issue Stepan Kasal
2014-06-11  9:37 ` [PATCH 4/7] MinGW: disable CRT command line globbing Stepan Kasal
2014-06-11  9:37 ` [PATCH 5/7] Win32: Unicode arguments (outgoing) Stepan Kasal
2014-06-11  9:37 ` [PATCH 6/7] Win32: Unicode arguments (incoming) Stepan Kasal
2014-06-11  9:37 ` [PATCH 7/7] Unicode file name support (gitk and git-gui) Stepan Kasal
2014-06-17  9:06 ` [PATCH 0/7] Second part of msysgit/unicode Karsten Blees
2014-06-18  3:05   ` Stepan Kasal
2014-06-18 17:33     ` Junio C Hamano
2014-06-18 21:35       ` Johannes Sixt [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=53A20610.80500@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=karsten.blees@gmail.com \
    --cc=kasal@ucw.cz \
    --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).