From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH 0/14] misc test-suite patches
Date: Sat, 18 Dec 2010 20:08:48 +0000 [thread overview]
Message-ID: <4D0D14D0.5020809@ramsay1.demon.co.uk> (raw)
In-Reply-To: <7v4oagt9zu.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
>> [PATCH 08/14] help.c: Fix detection of custom merge strategy on cygwin
>> [PATCH 09/14] t1301-*.sh: Fix the 'forced modes' test on cygwin
>
> I sense that there is something fundamentally wrong with the tricky l/stat
> emulation set-up code there, but I lack an expertise to judge if these two
> patches is going in the right direction. Help from people savvier on
> Windows issues than I is very much appreciated.
Just as a matter of interest, since I put some extra effort into writing
them, did you find the commit messages to be insufficient/unhelpful/confusing?
What could I have done better?
ATB,
Ramsay Jones
prev parent reply other threads:[~2010-12-18 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 18:17 [PATCH 0/14] misc test-suite patches Ramsay Jones
2010-12-14 19:44 ` Junio C Hamano
2010-12-18 20:08 ` Ramsay Jones [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=4D0D14D0.5020809@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--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.
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).