From: Matthieu Moy <matthieu.moy@grenoble-inp.fr>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Dr. George E. Moore" <gem@x-ctr-l.com>, git@vger.kernel.org
Subject: Re: Using git clone
Date: Sun, 9 Nov 2014 16:24:24 +0100 (CET) [thread overview]
Message-ID: <1094459024.7303740.1415546663657.JavaMail.zimbra@imag.fr> (raw)
In-Reply-To: <20141108171539.GB162918@vauxhall.crustytoothpaste.net>
----- Original Message -----
> You generally want to use git fetch or git pull in that case. git clone
> creates an entirely new copy of the original repository.
Just to complement the answer: "git clone" is more or less a shorthand for "git init" followed by "git fetch" (to get the remote objects) and "git checkout" (to get the actual files). The original poster probably doesn't want the "git init" part here indeed.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
prev parent reply other threads:[~2014-11-09 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 16:59 Using git clone Dr. George E. Moore
2014-11-08 17:15 ` brian m. carlson
2014-11-09 15:24 ` Matthieu Moy [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=1094459024.7303740.1415546663657.JavaMail.zimbra@imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=gem@x-ctr-l.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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).