All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Buchacher <drizzd@aon.at>
To: msysgit@googlegroups.com
Cc: git@vger.kernel.org
Subject: Illegal filename characters one Windows
Date: Sun, 15 Apr 2012 02:07:26 +0200	[thread overview]
Message-ID: <20120415000725.GA32140@ecki> (raw)

Hi,

I recently noticed that git does not deal very well with illegal
filenames on Windows. I have a repository which contains a couple of
filenames like "Re: some email.eml". On a Windows box, those files get
truncated to just "Re" during checkout, because ':' is an illegal
character for filenames on Windows. [1]

I know that the easiest solution would be to simply remove the illegal
characters on my Linux box and be done with it. But I dislike the fact
that git cannot handle such filenames more gracefully.

So I have been wondering how to fix this. I have considered converting
the filename to unicode or URL encoding or even just dropping the
illegal characters on checkout. But no matter which conversion I choose,
it will conflict with the converted filename, which would be a valid
index entry itself.

If a reasonable solution is not possible, maybe we should not try to
checkout such files at all, and mark them with --skip-worktree. That way
one can at least use such repositories, as long as one does not have to
touch any files with illegal characters in their filename. As it is,
most commands are not usable because the work tree is always dirty (the
files with illegal names have been "removed").

Any better ideas?

Clemens

[1] http://en.wikipedia.org/wiki/Filename

             reply	other threads:[~2012-04-15  0:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15  0:07 Clemens Buchacher [this message]
2012-04-15 17:16 ` [msysGit] Illegal filename characters one Windows Johannes Sixt

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=20120415000725.GA32140@ecki \
    --to=drizzd@aon.at \
    --cc=git@vger.kernel.org \
    --cc=msysgit@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.