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

Re: Interactive rebase encoding

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 15, 2008, 15:54 UTC
Message-ID
<alpine.DEB.1.00.0812151652400.30769@pacific.mpi-cbg.de>
In-Reply-To
<85647ef50812150442n48609eadl4f3e47fcc715e643@mail.gmail.com>
Hi,
On Mon, 15 Dec 2008, Constantine Plotnikov wrote:
Show 5 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.

As rebase -i does nothing else than piping the output of git log into a file (at least this is the first step), I thought it would be obvious that it uses the output encoding preferred by the user.

Indeed, I cannot think of any scenario where it might make sense to have a different encoding in git rebase -i than in git log.

Ciao, Dscho

Previous: Miklos VajnaNext: Constantine Plotnikov
Message 3 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.