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 example, Perforce on Windows often
From: Lars Schneider
Diff to v5:
* use "test_config" (Thanks Remi! I am still learning all the tools...)
* removed whitespaces (Thanks Luke! I added this to my "generate patch" script.
Won't happen again :-)
* added ACK from Luke (I interpreted "Looks good to me" that way. I hope this
is OK.)
On Thu, Sep 03, 2015 at 04:24:09AM -0400, Jeff King wrote:
> diff --git a/Documentation/technical/protocol-common.txt
> b/Documentation/technical/protocol-common.txt
> index 889985f..bf30167 100644
> --- a/Documentation/technical/protocol-common.txt
> +++ b/Documentation/technical/protocol-common
Hello!
Any help/pointers/advise regarding my request about dockerfile?
Thanks,
Atul.
On Tue, Sep 1, 2015 at 3:13 PM, Atul Sowani wrote:
> Hi,
>
> Greetings everybody!
>
> I am looking for a Dockerfile for git which will _build_ git from source on
> ppc64le platform. I want to build git with dif
On Thu, Sep 03, 2015 at 04:02:05AM -0400, Jeff King wrote:
> I'm also tempted to scrap this and say it just falls under the rule
> that every PKT-LINE is "sender SHOULD include LF" and "receiver MUST NOT
> complain about missing LF" (which does appear earlier in the document,
> though in a differe
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 . &&
> +git config git-p4
Junio C Hamano venit, vidit, dixit 27.07.2015 22:17:
> Antoine Beaupré writes:
>
>> Any reason why this patch wasn't included / reviewed?
>> ...
>>> This patch is similar than the one provided by Milton Soares Filho in
>>> 1382734287.31768.1.git.send.email.milton.soares.fi...@gmail.com but was
>>
Our pack-protocol spec indicates that a pushing client
should send ref update commands like:
$old_sha1 $new_sha1 $ref\n
with each ref update in its own pktline, with a trailing
newline. However, git itself does not follow this behavior;
it omits the trailing newline.
For the most part the dist
On Thursday, September 03, 2015 09:11:10 AM Sukhwinder Singh wrote:
> Hello,
>
> I have posted this question on various forums as well but I have not
> received any guidance yet. I was requesting some steps which I can follow.
> Our Servers are windows based.
Don't use windows. Get rid of people
101 - 109 of 109 matches
Mail list logo