Re: [PATCH v5] git-p4: add config git-p4.pathEncoding

2015-09-04 Thread Remi Galan Alfonso
Lars Schneider writes: > > Hi Lars, > > > > Lars Schneider writes: > > > >> +test_expect_success 'Clone repo containing iso8859-1 encoded paths with > >> git-p4.pathEncoding' ' > >> + > >> +test_when_finished cleanup_git && > >> +

Re: [PATCH v5] git-p4: add config git-p4.pathEncoding

2015-09-03 Thread Lars Schneider
On 03 Sep 2015, at 10:26, Remi Galan Alfonso wrote: > Hi Lars, > > Lars Schneider writes: > >> +test_expect_success 'Clone repo containing iso8859-1 encoded paths with >> git-p4.pathEncoding' ' >> + >> +

Re: [PATCH v5] git-p4: add config git-p4.pathEncoding

2015-09-03 Thread Remi Galan Alfonso
Hi Lars, Lars Schneider writes: > +test_expect_success 'Clone repo containing iso8859-1 encoded paths with > git-p4.pathEncoding' ' > + > +test_when_finished cleanup_git && > +( > +cd "$git" && > +git init . && > +

[PATCH v5] git-p4: add config git-p4.pathEncoding

2015-09-02 Thread larsxschneider
From: Lars Schneider Perforce keeps the encoding of a path as given by the originating OS. Git expects paths encoded as UTF-8. Add a config to tell git-p4 what encoding Perforce had used for the paths. This encoding is used to transcode the paths to UTF-8. As an

[PATCH v5] git-p4: add config git-p4.pathEncoding

2015-09-02 Thread larsxschneider
From: Lars Schneider Diff to v4: * add verbose output * reword help text * remove comment how to generate encoded sequence * use ascii characters in encoded sequence where possible * wrap 'cd' in TC in a subshell Thanks to Eric, Torsten, and Junio for feedback!

Re: [PATCH v5] git-p4: add config git-p4.pathEncoding

2015-09-02 Thread Luke Diamand
On 2 September 2015 at 21:39, wrote: > From: Lars Schneider > > Perforce keeps the encoding of a path as given by the originating OS. > Git expects paths encoded as UTF-8. Add a config to tell git-p4 what > encoding Perforce had used for the