From: "Torsten Bögershausen" <tboegi@web.de>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, tboegi@web.de, mhagger@alum.mit.edu,
mlevedahl@gmail.com, Jeff King <peff@peff.net>,
Johannes Sixt <j6t@kdbg.org>
Subject: Re: What's cooking in git.git (Jul 2013, #09; Mon, 29)
Date: Sat, 03 Aug 2013 08:50:08 +0200 [thread overview]
Message-ID: <51FCA820.9070907@web.de> (raw)
In-Reply-To: <51FACA67.8090207@ramsay1.demon.co.uk>
On 2013-08-01 22.51, Ramsay Jones wrote:
> Junio C Hamano wrote:
>> Ramsay Jones <ramsay@ramsay1.demon.co.uk> writes:
>>
>>>> I am personally in favor of this simpler solution. Comments?
>>>
>>> I had expected this to me marked for 'master'.
>>>
>>> Has this simply been overlooked, or do you have reservations about
>>> applying this patch?
>>
>> I am just being careful and do want to keep it cooking in 'next'
>> during the feature freeze. The more users work with 'next' (not
>> "work *on* 'next'"), the more confidence we would be with, and
>> hopefully this can be one of the topis that graduate early after
>> the 1.8.4 release.
>
> Hmm, this patch is a bug-fix for a bug that (currently) will be
> _introduced_ by v1.8.4.
>
> Do you want me to try and find a different bug-fix for v1.8.4?
> (Although that would most likely be more risky than simply taking
> this patch! ;-) ).
>
> ATB,
> Ramsay Jones
I just managed to run v1.8.4-rc1 under cygwin 1.7, and it all passed.
Good work, thanks.
I realized that core.filemode is true by default, which
by default switches of the stat()/lstat() code in cygwin.c
Which bug fix are we missing for v1.8.4 ?
/Torsten
next prev parent reply other threads:[~2013-08-03 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 22:43 What's cooking in git.git (Jul 2013, #09; Mon, 29) Junio C Hamano
2013-07-31 17:48 ` Ramsay Jones
2013-07-31 18:51 ` Junio C Hamano
2013-08-01 20:51 ` Ramsay Jones
2013-08-01 21:12 ` Junio C Hamano
2013-08-03 13:37 ` Mark Levedahl
2013-08-05 16:29 ` Junio C Hamano
2013-08-03 6:50 ` Torsten Bögershausen [this message]
2013-08-03 7:04 ` Torsten Bögershausen
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=51FCA820.9070907@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=mhagger@alum.mit.edu \
--cc=mlevedahl@gmail.com \
--cc=peff@peff.net \
--cc=ramsay@ramsay1.demon.co.uk \
/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).