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

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

From
Junio C Hamano <junkio@cox.net>
Date
Feb 4, 2007, 10:09 UTC
Message-ID
<7v4pq2tet5.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<e5bfff550702040200y4f09070fia3716ca949fddac7@mail.gmail.com>
"Marco Costalba" <mcostalba@gmail.com> writes:
Show 9 quoted lines
> On 2/4/07, Junio C Hamano <junkio@cox.net> wrote:
>> "Marco Costalba" <mcostalba@gmail.com> writes:
>>
>> > Probably you already now why I'm asking this ;-)
>>
>> No.  But we should certainly draw up deprecation/removal
>> schedule.  It simply could be "never" ;-).
>
> qgit needs to handle the text codec information 'i18n.commitencoding'
I thought you already fixed the header parser.  Is that a news?

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

Previous: Marco CostalbaNext: Marco Costalba
Message 4 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.