From: Maaartin <grajcar1@seznam.cz>
To: git@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: Locating Git Clone
Date: Wed, 19 Jan 2011 10:13:55 +0100 [thread overview]
Message-ID: <4D36AB53.6040105@seznam.cz> (raw)
In-Reply-To: <1295427449605-5938759.post@n2.nabble.com>
On 11-01-19 09:57, flebber wrote:
>
> So how can I determine which folder is set for git? Should I have declared
> the folder to clone to in the orginal clone command?
>
> I tried using --get-dir and the man.
>
> renshaw@RENSHAWRESIDENC ~
> $ --git-dir
> sh.exe": --git-dir: command not found
Wrong, it's a git option, i.e., you'd use something like
git --git-dir some_git_command ...
But you do NOT need it at all. Don't use it, it's a bit advanced. Just
change into the right directory before using any git command.
> renshaw@RENSHAWRESIDENC ~
> $ --git-dir=GIT_DIR
> sh.exe": --git-dir=GIT_DIR: command not found
>
> renshaw@RENSHAWRESIDENC ~
> $ help mv
> sh.exe": help: no help topics match `mv'. Try `help help'
> fo mv'.
>
> renshaw@RENSHAWRESIDENC ~
> $ man -k mv
> sh.exe": man: command not found
>
> renshaw@RENSHAWRESIDENC ~
> $ info mv
> sh.exe": info: command not found
Forget it,
http://www.google.com/search?q=man+mv
is what I use instead. It's fast enough for me.
> renshaw@RENSHAWRESIDENC ~
> $ mv grails-1.3.6 c:\grails
> mv: cannot stat `grails-1.3.6': No such file or directory
You did
git clone git://github.com/grails/grails-core.git
so I'd suppose you could move it using
mv grails-core c:/grails
Do not use "\" as it's an escape character, you'd need to double it. But
use anything you like for moving it.
next prev parent reply other threads:[~2011-01-19 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 8:35 Locating Git Clone flebber
2011-01-19 8:49 ` Alexey Shumkin
2011-01-19 8:57 ` flebber
2011-01-19 9:13 ` Maaartin [this message]
2011-01-19 10:28 ` flebber
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=4D36AB53.6040105@seznam.cz \
--to=grajcar1@seznam.cz \
--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).