Re: Cloning into an existing directory

From: Russell Steicke <russellsteicke@gmail.com>
Date: Feb 16, 2009, 07:31 UTC
Message-ID: <c1b8b6670902152331p9bbdb8fo7bf7048039b5301c@mail.gmail.com>
In-Reply-To: <e38bce640902152310x195a14e5p445817bdfc6e319f@mail.gmail.com>

On 2/16/09, Brent Goodrick <bgoodr@gmail.com> wrote:

Show 13 quoted lines

> Hi,
>
>  I would like to manage my startup scripts such as .bashrc and other
>  setup files relative to my HOME directory using Git. However,
>  git-clone disallows cloning into the existing "." directory, but only
>  allows cloning into a subdirectory that does not yet exist.  If my
>  home directory is /home/brentg and my remote repository is on
>  remote_machine:~brentg/my_setup.git then git clone in my home
>  directory on the local machine creates /home/brentg/my_setup with
>  files such as .bashrc inside it, which is not what I want. I want them
>  checked out and managed _in_ the current working directory, and not to
>  mess with other files or directories that already exist that are never
>  to be managed by git.

cd git init git remote add origin remote_machine:~brentg/my_setup.git git fetch git branch master origin/master git checkout master

You may have to delete .bashrc and others before git will overwrite them on checkout.

-- 
Virus found in this message.