Re: Cloning into an existing directory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/16/09, Brent Goodrick <bgoodr@xxxxxxxxx> wrote:
> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux