From: Junio C Hamano <gitster@pobox•com>
To: Pat Thoyts <patthoyts@users•sourceforge.net>
Cc: Git <git@vger•kernel.org>, msysGit <msysgit@googlegroups•com>
Subject: Re: [PATCH 0/7] Some patches from msysGit (round 2)
Date: Sat, 15 Oct 2011 22:17:23 -0700 [thread overview]
Message-ID: <7vsjmtsefw.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1318687520-19522-1-git-send-email-patthoyts@users.sourceforge.net> (Pat Thoyts's message of "Sat, 15 Oct 2011 15:05:13 +0100")
Pat Thoyts <patthoyts@users•sourceforge.net> writes:
> This collects some recent patches from the msysGit tree that clear up
> test issues on Windows.
>
> This second version incorporates suggestions received from round 1 to:
> avoid duplicating code in t9901 web-browse tests
> drop the t1402 changes in favour of another change from J6t (on pu)
> test for the presence of 'bcomp' in bc3 mergetool
Thanks.
Will replace the previous patches with these and advance them to 'next'
shortly.
prev parent reply other threads:[~2011-10-16 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 14:05 [PATCH 0/7] Some patches from msysGit (round 2) Pat Thoyts
2011-10-15 14:05 ` [PATCH 1/7] t1020: disable the pwd test on MinGW Pat Thoyts
2011-10-15 14:05 ` [PATCH 2/7] t9001: do not fail only due to CR/LF issues Pat Thoyts
2011-10-15 14:05 ` [PATCH 3/7] git-svn: On MSYS, escape and quote SVN_SSH also if set by the user Pat Thoyts
2011-10-15 14:05 ` [PATCH 4/7] t9901: fix line-ending dependency on windows Pat Thoyts
2011-10-15 14:05 ` [PATCH 5/7] t9300: do not run --cat-blob-fd related tests on MinGW Pat Thoyts
2011-10-15 14:05 ` [PATCH 6/7] mergetools: use the correct tool for Beyond Compare 3 on Windows Pat Thoyts
2011-10-15 14:05 ` [PATCH 7/7] mingw: ensure sockets are initialized before calling gethostname Pat Thoyts
2011-10-16 5:17 ` Junio C Hamano [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=7vsjmtsefw.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=msysgit@googlegroups$(echo .)com \
--cc=patthoyts@users$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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