From: Junio C Hamano Date: Mon, 04 Feb 2008 21:40:44 GMT Subject: Re: [PATCH 0 of 7] [resend] - Improve handling remotes, origin, submodules Message-ID: <7v1w7sjt7n.fsf@gitster.siamese.dyndns.org> In-Reply-To: Johannes Schindelin writes: > AFAICT "clone -o" was meant _only_ for this scenario: > > You have a slow connection, but someone can provide you with a thumb > drive, having the current repository. > > You clone it from the thumb drive, but of course you want to use your > (slow) connection for subsequent updates (i.e. you want to have a > different default remote). > > What you do is > > $ git clone -o thumbdrive /media/usbdisk/that-repository.git/ > > Then, to be able to update from your preferred remote quickly, you add the > proper remote: > > $ git remote add --fetch origin git://git.kernel.org/shlub.git/ > > In my understanding, this scenario is the only reason to live for clone's > -o option, and it would be actively wrong for it to change the _name_ of > the default remote to "thumbdrive". Then we should fix "git-clone". If you do the first command, I am reasonably sure that you would get: [branch "master"] remote = thumbdrive in your .git/config. You may want to occasionally go back to thumbdrive for sneakernetting, so I do not think we should remove [remote "thumbdrive"] section the clone would leave, but the above "master branch would interact with thumbdrive repository" should not be there. And that corrected behaviour and the intended use of -o should be documented.