Re: What's cooking in git.git (Sep 2011, #04; Mon, 12)

From: Jeff King <peff@peff.net>
Date: Sep 12, 2011, 23:33 UTC
Message-ID: <20110912233348.GE28994@sigill.intra.peff.net>
In-Reply-To: <7vwrdd1gyc.fsf@alter.siamese.dyndns.org>

On Mon, Sep 12, 2011 at 04:25:31PM -0700, Junio C Hamano wrote:

Show 6 quoted lines

> > Peff also asked if uppercase extensions are common on Windows. They
> > are, so one often sees .HTM, .HTML, etc. Should this issue be handled
> > by jk/default-attr?
> 
> I do not think we would mind adding .HTM but would people limit themselves
> to uppercase while not limiting themselves to three letters and use .HTML?

I wonder if they should all be in the style of:

  [Hh][Tt][Mm][Ll]
  [Jj][Aa][Vv][Aa]

for case-challenged systems. That feels like the wrong solution, though. If you're on a case-insensitive system, shouldn't we perhaps be comparing some kind of canonical version of the filename that is lowercased? That would help these built-in attributes, as well as ones that people write.

Or maybe that is too large a can of worms to open. I sort of assume we have those canonicalization routines somewhere already, though.

Show 6 quoted lines

> > Shouldn't the last entry be?
> >
> > 	"*.m diff=objc",
> 
> Thanks for spotting. I'll locally amend only this part and hope somebody
> would volunteer to submit an agreed version as the final one ;-)

I think we're missing Brandon's note that ".F" is used (as distinct from ".f", even on case-sensitive filesystems, as it has some magic meaning). And the pascal ones somebody mentioned.

-Peff