From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] i18n.pathencoding
Date: Tue, 04 Sep 2012 13:12:50 -0700 [thread overview]
Message-ID: <7vy5kp8s3h.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <50465BBC.30203@web.de> ("Torsten =?utf-8?Q?B=C3=B6gershausen?= =?utf-8?Q?=22's?= message of "Tue, 04 Sep 2012 21:51:24 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> 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.
next prev parent reply other threads:[~2012-09-04 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 6:11 [RFC] i18n.pathencoding Torsten Bögershausen
2012-09-02 22:59 ` Robin Rosenberg
2012-09-08 10:09 ` Torsten Bögershausen
2012-09-04 12:23 ` Nguyen Thai Ngoc Duy
2012-09-04 17:19 ` Junio C Hamano
2012-09-04 19:51 ` Torsten Bögershausen
2012-09-04 20:12 ` Junio C Hamano [this message]
2012-09-05 19:52 ` Torsten Bögershausen
2012-09-05 11:11 ` Nguyen Thai Ngoc Duy
2012-09-05 19:49 ` Torsten Bögershausen
2012-09-06 3:24 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vy5kp8s3h.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=tboegi@web.de \
/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.