git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Luke Diamand <luke@diamand.org>
Date
Sep 2, 2015, 21:32 UTC
Message-ID
<CAE5ih7_Kje_Qrz7zKH4uSGziVpdp6VqsZf7hSMwQkvta97CG9w@mail.gmail.com>
In-Reply-To
<1441226355-61103-2-git-send-email-larsxschneider@gmail.com>
On 2 September 2015 at 21:39,  <larsxschneider@gmail.com> wrote:
Show 7 quoted lines
> From: Lars Schneider <larsxschneider@gmail.com>
>
> 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
> uses “cp1252” to encode path names.
Looks good to me, and the test passes.
Note that git diff --check complains about a trailing whitespace.
Previous: larsxschneider@gmail.comNext: Remi Galan Alfonso
Message 3 of 6 in “git-p4: add config git-p4.pathEncoding”
  1. git-p4: add config git-p4.pathEncodinglarsxschneider@gmail.com, Sep 2, 2015
  2. git-p4: add config git-p4.pathEncodinglarsxschneider@gmail.com, Sep 2, 2015
  3. Luke DiamandSep 2, 2015
  4. Remi Galan AlfonsoSep 3, 2015
  5. Lars SchneiderSep 3, 2015
  6. Remi Galan AlfonsoSep 4, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.