git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
	Brian Gernhardt <brian@gernhardtsoftware.com>,
	"git@vger.kernel.org List" <git@vger.kernel.org>
Subject: Re: t3010 broken by 2eac2a4
Date: Fri, 23 Aug 2013 14:51:58 -0400	[thread overview]
Message-ID: <20130823185158.GC30130@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqk3jcpbuc.fsf@gitster.dls.corp.google.com>

On Fri, Aug 23, 2013 at 10:15:55AM -0700, Junio C Hamano wrote:

> When 5102c617 (Add case insensitivity support for directories when
> using git status, 2010-10-03) added the directories to the name-hash
> with trailing slash, there was only a single name hash table to
> which both real cache entries and leading directory prefixes are
> registered, so it made some sense to register them with trailing
> slashes so that we can tell what kind of entry is being returned.
> 
> But since 2092678c (name-hash.c: fix endless loop with
> core.ignorecase=true, 2013-02-28), these directory entries that are
> not the cache entries are kept track of in a separate hashtable,
> which makes me wonder if it still makes sense to register
> directories with trailing slashes.
> 
> And if we stop doing that (and instead if we shrunk the namelen when
> an unconverted caller asks for a name with a trailing slash to see
> if a directory exists in the index), wouldn't it automatically fix
> the directory_exists_in_index_icase()?  It does not need to assume
> that dirname[len] has '/'; after all, it may not even be a valid
> memory location in the first place.

Yeah, I think that is sane overall direction. When I did the sketch that
eventually turned into Karsten's 2092678c, that was one of the goals.
But I did not keep up with his response and the final patch, and I'm not
sure if the slashes still serve some function. So it would definitely
need somebody looking carefully at the current logic.

More details are in this sub-thread:

  http://thread.gmane.org/gmane.comp.version-control.git/215820/focus=216284

-Peff

      reply	other threads:[~2013-08-23 18:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 20:31 t3010 broken by 2eac2a4 Brian Gernhardt
2013-08-21 21:41 ` Junio C Hamano
2013-08-22 20:54   ` Eric Sunshine
2013-08-22 21:16     ` Junio C Hamano
2013-08-22 21:22       ` Eric Sunshine
2013-08-22 21:32         ` Junio C Hamano
2013-08-22 21:35           ` Eric Sunshine
2013-08-22 21:43             ` Junio C Hamano
2013-08-22 21:59               ` Eric Sunshine
2013-08-22 22:53                 ` Eric Sunshine
2013-08-22 23:12                   ` Junio C Hamano
2013-08-22 23:15                     ` Eric Sunshine
2013-08-23  4:32                       ` Eric Sunshine
2013-08-23  5:36                         ` Junio C Hamano
2013-08-23  9:19                           ` Eric Sunshine
2013-08-23 17:15                             ` Junio C Hamano
2013-08-23 18:51                               ` Jeff King [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=20130823185158.GC30130@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=brian@gernhardtsoftware.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sunshine@sunshineco.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).