git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: Thomas Singer <thomas.singer@syntevo.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	EGit developer discussion <egit-dev@eclipse.org>,
	Marc Strapetz <marc.strapetz@syntevo.com>,
	git@vger.kernel.org
Subject: Re: [egit-dev] Re: jgit problems for file paths with  non-ASCII	characters
Date: Thu, 26 Nov 2009 17:44:43 +0100	[thread overview]
Message-ID: <200911261744.43917.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <4B0E7DF5.9040007@syntevo.com>

torsdag 26 november 2009 14:09:09 skrev  Thomas Singer:
> > But as you said, this still doesn't make the Apple normal form
> > any easier.  Though if we know we are on such a strange filesystem
> > we might be able to assume the paths in the repository are equally
> > damaged.  Or not.
>
> Well, if the git-core folks could standardize on, e.g., composed UTF-8
> (rather then just UTF-8), for storing file names in the repository, then
> everything should be clear, isn't it?

Hey, we're trying to enforce composed characters...

-- robin

  parent reply	other threads:[~2009-11-26 16:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 13:47 jgit problems for file paths with non-ASCII characters Marc Strapetz
2009-11-25 21:11 ` Robin Rosenberg
2009-11-26  0:54   ` [egit-dev] " Shawn O. Pearce
2009-11-26 13:09     ` Thomas Singer
2009-11-26 14:47       ` Johannes Schindelin
2009-11-26 15:31         ` Thomas Singer
2009-11-26 19:57           ` Shawn O. Pearce
2009-11-26 16:44       ` Robin Rosenberg [this message]
2009-11-26 14:25     ` Marc Strapetz
2009-11-26 20:03       ` Shawn O. Pearce

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=200911261744.43917.robin.rosenberg@dewire.com \
    --to=robin.rosenberg@dewire.com \
    --cc=egit-dev@eclipse.org \
    --cc=git@vger.kernel.org \
    --cc=marc.strapetz@syntevo.com \
    --cc=spearce@spearce.org \
    --cc=thomas.singer@syntevo.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).