public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg•org>
To: Clemens Buchacher <drizzd@aon•at>
Cc: msysgit@googlegroups•com, git@vger•kernel.org
Subject: Re: [msysGit] Illegal filename characters one Windows
Date: Sun, 15 Apr 2012 19:16:29 +0200	[thread overview]
Message-ID: <4F8B026D.5070505@kdbg.org> (raw)
In-Reply-To: <20120415000725.GA32140@ecki>

Am 15.04.2012 02:07, schrieb Clemens Buchacher:
> 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]

This is a issue very similar to files named nul, aux, prn, com1 and the
like; they can't be checked out, either. I've suggested to use sparse
checkout in such cases; other than that, I think we don't have a
solution for it.

-- Hannes

      reply	other threads:[~2012-04-15 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15  0:07 Illegal filename characters one Windows Clemens Buchacher
2012-04-15 17:16 ` Johannes Sixt [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=4F8B026D.5070505@kdbg.org \
    --to=j6t@kdbg$(echo .)org \
    --cc=drizzd@aon$(echo .)at \
    --cc=git@vger$(echo .)kernel.org \
    --cc=msysgit@googlegroups$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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