{"thread":{"id":"7743","subject":"How to make a repository config up-to-date","startedAt":"2007-04-19T23:45:32Z","lastAt":"2007-04-20T12:34:55Z","messageCount":3,"participants":["Olivier Galibert","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"39925","messageId":"20070419234532.GA38838@dspnet.fr.eu.org","threadId":"7743","inReplyTo":null,"subject":"How to make a repository config up-to-date","fromName":"Olivier Galibert","fromEmail":"galibert@pobox.com","sentAt":"2007-04-19T23:45:32Z","receivedAt":"2007-04-19T23:45:32Z","isPatch":false,"sender":{"key":"galibert@pobox.com","avatar":null},"body":"I've got a number of a little over one year old repositories I do my\nprivate stuff into.  Looks like in that year things changed quite a\nbit (remote going from files to some kind of config file?  reflog\nstuff?).  What should I do to change them to what would be considered\nan up-to-date, full bells-and-whistles configuration?\n\n  OG.\n"},{"id":"39926","messageId":"7v7is76h8c.fsf@assigned-by-dhcp.cox.net","threadId":"7743","inReplyTo":"20070419234532.GA38838@dspnet.fr.eu.org","subject":"Re: How to make a repository config up-to-date","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-04-20T00:07:31Z","receivedAt":"2007-04-20T00:07:31Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Olivier Galibert <galibert@pobox.com> writes:\n\n> I've got a number of a little over one year old repositories I do my\n> private stuff into.  Looks like in that year things changed quite a\n> bit (remote going from files to some kind of config file?  reflog\n> stuff?).  What should I do to change them to what would be considered\n> an up-to-date, full bells-and-whistles configuration?\n\nA better question to ask before that is \"do I need to change to\ntake advantage of any bells-and-whistles\", I think.\n\n* To enable reflog in your repository with working-tree, you do\n  not have to do anything.  It's on by default.\n\n* $GIT_DIR/remotes/origin is still consulted for a pull/fetch.\n  If you do not do complicated multi-branch workflow, you do not\n  gain much by moving that information to .git/config.\n\nThere is a contrib/remotes2config.sh script that copies\ninformation from remotes/origin into .git/config if you are\ninterested.\n"},{"id":"39973","messageId":"20070420123455.GA62110@dspnet.fr.eu.org","threadId":"7743","inReplyTo":"7v7is76h8c.fsf@assigned-by-dhcp.cox.net","subject":"Re: How to make a repository config up-to-date","fromName":"Olivier Galibert","fromEmail":"galibert@pobox.com","sentAt":"2007-04-20T12:34:55Z","receivedAt":"2007-04-20T12:34:55Z","isPatch":false,"sender":{"key":"galibert@pobox.com","avatar":null},"body":"On Thu, Apr 19, 2007 at 05:07:31PM -0700, Junio C Hamano wrote:\n> A better question to ask before that is \"do I need to change to\n> take advantage of any bells-and-whistles\", I think.\n\nIndeed.\n\n\n> * To enable reflog in your repository with working-tree, you do\n>   not have to do anything.  It's on by default.\n\nAh nice :-)\n\n\n> * $GIT_DIR/remotes/origin is still consulted for a pull/fetch.\n>   If you do not do complicated multi-branch workflow, you do not\n>   gain much by moving that information to .git/config.\n> \n> There is a contrib/remotes2config.sh script that copies\n> information from remotes/origin into .git/config if you are\n> interested.\n\nExcellent, I'll check the result and decide whether it seems worth it.\n\n  OG.\n"}]}