From: Russell Steicke <russellsteicke@gmail.com>
To: Brent Goodrick <bgoodr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Cloning into an existing directory
Date: Mon, 16 Feb 2009 07:31:55 +0000 [thread overview]
Message-ID: <c1b8b6670902152331p9bbdb8fo7bf7048039b5301c@mail.gmail.com> (raw)
In-Reply-To: <e38bce640902152310x195a14e5p445817bdfc6e319f@mail.gmail.com>
On 2/16/09, Brent Goodrick <bgoodr@gmail.com> 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.
next prev parent reply other threads:[~2009-02-16 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 7:10 Cloning into an existing directory Brent Goodrick
2009-02-16 7:31 ` Russell Steicke [this message]
2009-02-16 16:13 ` Brent Goodrick
2009-02-16 16:48 ` Andrew Ruder
2009-02-17 2:53 ` Brent Goodrick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1b8b6670902152331p9bbdb8fo7bf7048039b5301c@mail.gmail.com \
--to=russellsteicke@gmail.com \
--cc=bgoodr@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).