* How to make a repository config up-to-date
@ 2007-04-19 23:45 Olivier Galibert
2007-04-20 0:07 ` Junio C Hamano
0 siblings, 1 reply; 3+ messages in thread
From: Olivier Galibert @ 2007-04-19 23:45 UTC (permalink / raw)
To: git
I've got a number of a little over one year old repositories I do my
private stuff into. Looks like in that year things changed quite a
bit (remote going from files to some kind of config file? reflog
stuff?). What should I do to change them to what would be considered
an up-to-date, full bells-and-whistles configuration?
OG.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How to make a repository config up-to-date
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
0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2007-04-20 0:07 UTC (permalink / raw)
To: Olivier Galibert; +Cc: git
Olivier Galibert <galibert@pobox.com> writes:
> I've got a number of a little over one year old repositories I do my
> private stuff into. Looks like in that year things changed quite a
> bit (remote going from files to some kind of config file? reflog
> stuff?). What should I do to change them to what would be considered
> an up-to-date, full bells-and-whistles configuration?
A better question to ask before that is "do I need to change to
take advantage of any bells-and-whistles", I think.
* To enable reflog in your repository with working-tree, you do
not have to do anything. It's on by default.
* $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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How to make a repository config up-to-date
2007-04-20 0:07 ` Junio C Hamano
@ 2007-04-20 12:34 ` Olivier Galibert
0 siblings, 0 replies; 3+ messages in thread
From: Olivier Galibert @ 2007-04-20 12:34 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-04-20 12:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).