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

Re: How to make a repository config up-to-date

From
OGOlivier Galibert <galibert@pobox.com>
Date
Apr 20, 2007, 12:34 UTC
Message-ID
<20070420123455.GA62110@dspnet.fr.eu.org>
In-Reply-To
<7v7is76h8c.fsf@assigned-by-dhcp.cox.net>
On Thu, Apr 19, 2007 at 05:07:31PM -0700, Junio C Hamano wrote:
> A better question to ask before that is "do I need to change to
> take advantage of any bells-and-whistles", I think.
Indeed.
> * To enable reflog in your repository with working-tree, you do
>   not have to do anything.  It's on by default.
Ah nice :-)
Show 7 quoted lines
> * $GIT_DIR/remotes/origin is still consulted for a pull/fetch.
>   If you do not do complicated multi-branch workflow, you do not
>   gain much by moving that information to .git/config.
> 
> There is a contrib/remotes2config.sh script that copies
> information from remotes/origin into .git/config if you are
> interested.
Excellent, I'll check the result and decide whether it seems worth it.
  OG.
Previous: Junio C Hamano
Message 3 of 3 in “How to make a repository config up-to-date”
  1. Olivier GalibertApr 19, 2007
  2. Junio C HamanoApr 20, 2007
  3. Olivier GalibertApr 20, 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.