git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2010, #06; Tue, 21)
Date: Fri, 24 Dec 2010 13:02:12 -0700	[thread overview]
Message-ID: <4D14FC44.5070309@workspacewhiz.com> (raw)
In-Reply-To: <7vzkrvynz5.fsf@alter.siamese.dyndns.org>

----- Original Message -----
From: Junio C Hamano
Date: 12/24/2010 12:23 PM
> Joshua Jensen<jjensen@workspacewhiz.com>  writes:
>
>> Having said that, I have had 100 people using the jj/icase-directory
>> series on Windows daily for 4 months now without issue.  Prior to
>> that, a majority of the series had been used for a full year by a
>> dozen people....
> Just to make sure nobody misunderstood me, what I was proposing to put on
> hold was not the "case insensitivity" work of yours, which is already
> scheduled to be part of the coming release.
Ah.  I completely misinterpreted your statement.

Well, that's exciting.  After it goes live, I'll have some more case 
insensitivity patches forthcoming for discussion.

-Josh

  reply	other threads:[~2010-12-24 20:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22  1:59 What's cooking in git.git (Dec 2010, #06; Tue, 21) Junio C Hamano
2010-12-22 11:05 ` Thiago Farina
2010-12-22 11:39   ` Andreas Ericsson
2010-12-22 20:48   ` Junio C Hamano
2010-12-22 23:08     ` Thiago Farina
2010-12-23 15:52 ` Heiko Voigt
2010-12-23 16:32 ` Nguyen Thai Ngoc Duy
2010-12-23 17:17   ` Junio C Hamano
2010-12-23 23:35     ` Joshua Jensen
2010-12-24  1:39       ` Nguyen Thai Ngoc Duy
2010-12-24 16:53         ` Joshua Jensen
2010-12-25  2:20           ` Nguyen Thai Ngoc Duy
2010-12-24 19:23       ` Junio C Hamano
2010-12-24 20:02         ` Joshua Jensen [this message]
2010-12-24  1:33     ` Nguyen Thai Ngoc Duy
2010-12-26 10:46 ` Thomas Rast
2010-12-26 19:28   ` Junio C Hamano

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=4D14FC44.5070309@workspacewhiz.com \
    --to=jjensen@workspacewhiz.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.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).