From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
git@vger.kernel.org, Boaz Harrosh <bharrosh@panasas.com>,
Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>,
Thomas Rast <trast@student.ethz.ch>,
Alexey Shumkin <zapped@mail.ru>
Subject: Re: What's cooking in git.git (Sep 2011, #04; Mon, 12)
Date: Mon, 12 Sep 2011 19:33:48 -0400 [thread overview]
Message-ID: <20110912233348.GE28994@sigill.intra.peff.net> (raw)
In-Reply-To: <7vwrdd1gyc.fsf@alter.siamese.dyndns.org>
On Mon, Sep 12, 2011 at 04:25:31PM -0700, Junio C Hamano wrote:
> > 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.
> > 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
next prev parent reply other threads:[~2011-09-12 23:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 20:16 What's cooking in git.git (Sep 2011, #04; Mon, 12) Junio C Hamano
2011-09-12 21:48 ` Junio C Hamano
2011-09-12 21:51 ` Junio C Hamano
2011-09-12 23:27 ` Jeff King
2011-09-13 0:09 ` Junio C Hamano
2011-09-13 9:24 ` Nguyen Thai Ngoc Duy
2011-09-12 21:53 ` Junio C Hamano
2011-09-13 7:32 ` [PATCH v2] Documentation: basic configuration of notes.rewriteRef Thomas Rast
2011-09-13 17:16 ` Junio C Hamano
2011-09-13 17:18 ` Jeff King
2011-09-12 21:55 ` What's cooking in git.git (Sep 2011, #04; Mon, 12) Junio C Hamano
2011-09-12 21:59 ` Junio C Hamano
2011-09-14 2:34 ` Jonathon Mah
2011-09-14 20:57 ` Junio C Hamano
2011-09-16 2:12 ` [PATCH] mergetool: Use args as pathspec to unmerged files Jonathon Mah
2011-09-16 20:17 ` Junio C Hamano
2011-09-25 0:45 ` David Aguilar
2011-09-26 16:40 ` Junio C Hamano
2011-09-12 22:02 ` What's cooking in git.git (Sep 2011, #04; Mon, 12) Junio C Hamano
2011-09-12 23:15 ` Sverre Rabbelier
2011-09-12 22:56 ` Junio C Hamano
2011-09-13 9:46 ` Erik Faye-Lund
2011-09-29 12:03 ` Pascal Obry
2011-09-12 22:58 ` Junio C Hamano
2011-09-13 12:05 ` Michael J Gruber
[not found] ` <7vk49d5t8u.fsf@alter.siamese.dyndns.org>
2011-09-12 23:15 ` Eric Sunshine
2011-09-12 23:25 ` Junio C Hamano
2011-09-12 23:33 ` Jeff King [this message]
2011-09-12 23:53 ` Jeff King
2011-09-13 15:15 ` Brandon Casey
2011-09-13 16:05 ` Jeff King
2011-09-13 16:22 ` Brandon Casey
2011-09-13 7:51 ` John Szakmeister
2011-09-13 15:04 ` Eric Sunshine
2011-09-13 17:20 ` Jeff King
2011-09-12 23:35 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110912233348.GE28994@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=bharrosh@panasas.com \
--cc=brandon.casey.ctr@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.com \
--cc=trast@student.ethz.ch \
--cc=zapped@mail.ru \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).