From: Olivier Galibert <galibert@pobox.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: How to make a repository config up-to-date
Date: Fri, 20 Apr 2007 14:34:55 +0200 [thread overview]
Message-ID: <20070420123455.GA62110@dspnet.fr.eu.org> (raw)
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 :-)
> * $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.
prev parent reply other threads:[~2007-04-20 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 23:45 How to make a repository config up-to-date Olivier Galibert
2007-04-20 0:07 ` Junio C Hamano
2007-04-20 12:34 ` Olivier Galibert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070420123455.GA62110@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).