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

Re: [PATCH] gitk branch name encoding utf-8 probrem

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Dec 4, 2019, 22:29 UTC
Message-ID
<20191204222921.GB195537@google.com>
In-Reply-To
<TY2PR01MB24271C32E2FD9FD8C27CA8C2CA5D0@TY2PR01MB2427.jpnprd01.prod.outlook.com>

(cc-ing Paul, gitk expert) Hi!

加藤一博 wrote:
> Here is a patch to gitk branch name utf-8 probrem.

Thanks for reporting it. Can you provide a short summary here of the problem that we can use for a self-contained description in the commit log? See https://www.kernel.org/pub/software/scm/git/docs/SubmittingPatches.html#describe-changes for more on this subject.

May we also have your sign-off? See https://www.kernel.org/pub/software/scm/git/docs/SubmittingPatches.html#sign-off for what this means.

Thanks and hope that helps, Jonathan

Show 28 quoted lines
> See issue
> https://github.com/kkato233/gitk/issues/1
> and fix it 
> https://github.com/kkato233/gitk/pull/2
> 
> 
> ---
> 
> diff --git a/gitk b/gitk
> index abe4805..3f61a5b 100755
> --- a/gitk
> +++ b/gitk
> @@ -1780,11 +1780,15 @@ proc readrefs {} {
>      global otherrefids idotherrefs mainhead mainheadid
>      global selecthead selectheadid
>      global hideremotes
> +    global tclencoding
> 
>      foreach v {tagids idtags headids idheads otherrefids idotherrefs} {
>         unset -nocomplain $v
>      }
>      set refd [open [list | git show-ref -d] r]
> +    if {$tclencoding != {}} {
> +       fconfigure $refd -encoding $tclencoding
> +    }
>      while {[gets $refd line] >= 0} {
>         if {[string index $line 40] ne " "} continue
>         set id [string range $line 0 39]
Previous: 加藤一博Next: 加藤一博
Message 2 of 6 in “gitk branch name encoding utf-8 probrem”
  1. gitk branch name encoding utf-8 probrem加藤一博, Dec 4, 2019
  2. Jonathan NiederDec 4, 2019
  3. gitk branch name encoding utf-8 probrem加藤一博, Dec 5, 2019
  4. Junio C HamanoDec 5, 2019
  5. Pratyush YadavDec 5, 2019
  6. Pratyush YadavDec 5, 2019

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.