Re: [RFC] i18n.pathencoding

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 4, 2012, 20:12 UTC
Message-ID: <7vy5kp8s3h.fsf@alter.siamese.dyndns.org>
In-Reply-To: <50465BBC.30203@web.de>

Torsten Bögershausen <tboegi@web.de> writes:

Show 5 quoted lines

> This leads to 2 questions:
> a) Do we want the reencode feature in git, so that I continue to work on it?
>    From a performance point of view that would probably OK:
>    The "git status" on a linux tree was slightly slower on my PC when measured with time.
>    From the user experience there was not a difference.

I am not fundamentally opposed to such a change, as long as the change does not affect performance at all when the feature is not used, and the resulting code does not become too ugly.

Use of the "reencode" feature may have to make things slow, but you have to spend some cycle to do what the feature has to do anyway, so...

> b) If yes,
>    I have to admit that I don't use paths from --stdin or file so much,
>    except "git am" or "git format-patch"
>    Which commands are affected?

$ git grep -l -e '--stdin' Documentation/git*

may be a good starting point.