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

Re: Interactive rebase encoding

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Dec 15, 2008, 15:13 UTC
Message-ID
<20081215151322.GI5691@genesis.frugalware.org>
In-Reply-To
<85647ef50812150442n48609eadl4f3e47fcc715e643@mail.gmail.com>
On Mon, Dec 15, 2008 at 03:42:08PM +0300, Constantine Plotnikov <constantine.plotnikov@gmail.com> wrote:
Show 6 quoted lines
> The interactive rebase command builds a text file and passes it to
> editor specified as environment variable or as configuration
> parameter. However the man page for rebase operation says nothing
> about which encoding will be used for that file. Apparently
> i18n.logoutputencoding is used. I think that the man page for rebase
> operation should explicitly specify it.
Care to send a patch?
> Also it might make sense to use explicit encoding parameter for
> interactive rebase operation.

Do you have a use-case where having a different encoding for log output and rebase -i todo list makes sense?

Thanks.
Previous: Constantine PlotnikovNext: Johannes Schindelin
Message 2 of 5 in “Interactive rebase encoding”
  1. Constantine PlotnikovDec 15, 2008
  2. Miklos VajnaDec 15, 2008
  3. Johannes SchindelinDec 15, 2008
  4. Constantine PlotnikovDec 15, 2008
  5. Johannes SchindelinDec 15, 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.