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

Re: 'git config' vs 'git repo-config'

From
MCMarco Costalba <mcostalba@gmail.com>
Date
Feb 4, 2007, 10:23 UTC
Message-ID
<e5bfff550702040223h56f1524x9e6c460445874063@mail.gmail.com>
In-Reply-To
<7v4pq2tet5.fsf@assigned-by-dhcp.cox.net>
On 2/4/07, Junio C Hamano <junkio@cox.net> wrote:
Show 7 quoted lines
> "Marco Costalba" <mcostalba@gmail.com> writes:
>
> >
> > qgit needs to handle the text codec information 'i18n.commitencoding'
>
> I thought you already fixed the header parser.  Is that a news?
>
The parser is fixed from some week already.

Codec info is shown to user when opens settings dialog and could be manually set by user there. If not present utf8 is assumed.

> I wonder what it has to do with the command deprecation/removal
> schedule...
>

I plan to release a point release after git-1.5 is out, so I'm wondering if renaming git-repo-config --> git-config also in qgit.

BTW  'git-repo-config' seems to be currently used also by StGit
Previous: Junio C HamanoNext: Jakub Narebski
Message 5 of 7 in “'git config' vs 'git repo-config'”
  1. Marco CostalbaFeb 4, 2007
  2. Junio C HamanoFeb 4, 2007
  3. Marco CostalbaFeb 4, 2007
  4. Junio C HamanoFeb 4, 2007
  5. Marco CostalbaFeb 4, 2007
  6. Jakub NarebskiFeb 4, 2007
  7. Junio C HamanoFeb 4, 2007

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.