From: Brent Goodrick <bgoodr@gmail.com>
To: Andrew Ruder <andy@aeruder.net>
Cc: git@vger.kernel.org
Subject: Re: Cloning into an existing directory
Date: Mon, 16 Feb 2009 18:53:17 -0800 [thread overview]
Message-ID: <e38bce640902161853s20d44f5bmde42713ab66963df@mail.gmail.com> (raw)
In-Reply-To: <a030d93b0902160848x1c0521c3jb5ed2f1bf865a097@mail.gmail.com>
On Mon, Feb 16, 2009 at 8:48 AM, Andrew Ruder <andy@aeruder.net> wrote:
>
> On Mon, Feb 16, 2009 at 9:13 AM, Brent Goodrick <bgoodr@gmail.com> wrote:
> > 1. Move aside each file it complains about
> > 2. Run the git-checkout command again
> > 3. Move each file back to their original names, thus creating a local
> > edit w.r.t. git
>
> Actually, on my git (1.6.0.4) this just magically works due to the
> fact that 'git init' sets up the repository with HEAD pointing to
> refs/heads/master (which doesn't exist yet) and you go ahead and
> create the master branch with the 'git branch' command.
>
> In other words, in this particular situation the 'git checkout'
> command is completely unnecessary and if you just run a 'git status'
> you should already see that git sees all the differences already as
> local edits (assuming you didn't call you branch in the 'git branch'
> step something other than master).
Well, it does show them as local edits, and actually shows the file as
deleted. I ended up having to do a git-add on those files and commit
them, which will work for me.
bg
prev parent reply other threads:[~2009-02-17 2:54 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
2009-02-16 16:13 ` Brent Goodrick
2009-02-16 16:48 ` Andrew Ruder
2009-02-17 2:53 ` Brent Goodrick [this message]
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=e38bce640902161853s20d44f5bmde42713ab66963df@mail.gmail.com \
--to=bgoodr@gmail.com \
--cc=andy@aeruder.net \
--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).