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

Re: [PATCH (GITK)] gitk: Fix commit encoding support.

From
Paul Mackerras <paulus@samba.org>
Date
Nov 13, 2008, 11:42 UTC
Message-ID
<18716.4802.663635.847263@cargo.ozlabs.ibm.com>
In-Reply-To
<bb6f213e0811100406l2fcde5b8k8772360947b948fd@mail.gmail.com>
Alexander Gavrilov writes:
Show 5 quoted lines
> If all commits were loaded through cat-file, that would be the way to
> go. Otherwise, when one code path uses one method of conversion, and
> another one, which is used rarely and semi-randomly, a different
> method, it may lead to confusing results if something goes slightly
> wrong.

OK, that makes sense. I applied the patch with a paragraph added to the description that explains that.

Thanks, Paul.

Previous: Alexander Gavrilov
Message 4 of 4 in “gitk: Fix commit encoding support.”
  1. gitk: Fix commit encoding support.Alexander Gavrilov, Nov 9, 2008
  2. Paul MackerrasNov 10, 2008
  3. Alexander GavrilovNov 10, 2008
  4. Paul MackerrasNov 13, 2008

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.