On Wed, Sep 5, 2012 at 12:19 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyen Thai Ngoc Duy pclo...@gmail.com writes:
On Sat, Sep 1, 2012 at 1:11 PM, Torsten Bögershausen tbo...@web.de wrote:
@@ -476,7 +476,7 @@ int parse_options(int argc, const char **argv, const
char *prefix,
On 05.09.12 13:11, Nguyen Thai Ngoc Duy wrote:
On Wed, Sep 5, 2012 at 12:19 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyen Thai Ngoc Duy pclo...@gmail.com writes:
On Sat, Sep 1, 2012 at 1:11 PM, Torsten Bögershausen tbo...@web.de wrote:
@@ -476,7 +476,7 @@ int parse_options(int argc, const
On 04.09.12 22:12, Junio C Hamano wrote:
Torsten Bögershausen tbo...@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
Torsten Bögershausen tbo...@web.de writes:
On 05.09.12 13:11, Nguyen Thai Ngoc Duy wrote:
On Wed, Sep 5, 2012 at 12:19 AM, Junio C Hamano gits...@pobox.com wrote:
Nguyen Thai Ngoc Duy pclo...@gmail.com writes:
On Sat, Sep 1, 2012 at 1:11 PM, Torsten Bögershausen tbo...@web.de wrote:
@@
On Sat, Sep 1, 2012 at 1:11 PM, Torsten Bögershausen tbo...@web.de wrote:
diff --git a/parse-options.c b/parse-options.c
index c1c66bd..5840c18 100644
--- a/parse-options.c
+++ b/parse-options.c
@@ -476,7 +476,7 @@ int parse_options(int argc, const char **argv, const char
*prefix,
Nguyen Thai Ngoc Duy pclo...@gmail.com writes:
On Sat, Sep 1, 2012 at 1:11 PM, Torsten Bögershausen tbo...@web.de wrote:
diff --git a/parse-options.c b/parse-options.c
index c1c66bd..5840c18 100644
--- a/parse-options.c
+++ b/parse-options.c
@@ -476,7 +476,7 @@ int parse_options(int argc,
On 04.09.12 19:19, Junio C Hamano wrote:
Nguyen Thai Ngoc Duy pclo...@gmail.com writes:
On Sat, Sep 1, 2012 at 1:11 PM, Torsten Bögershausen tbo...@web.de wrote:
diff --git a/parse-options.c b/parse-options.c
index c1c66bd..5840c18 100644
--- a/parse-options.c
+++ b/parse-options.c
@@
Torsten Bögershausen tbo...@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
Torsten Bögershausen skrev 2012-09-01 08.11: Allow path names to be encoded in
UTF-8 in the repository
and checkout out as e.g. ISO-8859-1 in the working tree.
Ack for attempting this.
Did it myself if 2007, but times weren't ripe then, I guess.
+i18n.pathEncoding::
+ This option is only
Allow path names to be encoded in UTF-8 in the repository
and checkout out as e.g. ISO-8859-1 in the working tree.
Introduce a config variable i18n.pathEncoding.
If empty, no re-encoding of path names is done.
Add t3911 to test encoding back and forth
The re-encoding is done in
10 matches
Mail list logo