From: Jonathan Nieder <jrnieder@gmail.com>
To: sandy2010 <sandeeptt@yahoo.com>
Cc: git@vger.kernel.org, Joshua Juran <jjuran@gmail.com>
Subject: Re: git commands
Date: Fri, 20 Aug 2010 02:51:11 -0500 [thread overview]
Message-ID: <20100820075111.GC24678@burratino> (raw)
In-Reply-To: <1282288658094-5443370.post@n2.nabble.com>
sandy2010 wrote:
> I'm new to git and I wonder what is the difference between two commands:
>
> "git clone" and "git-clone" and which one should be use?
By the way, when documentation points to the latter (and is not
pointing to some man page like git-clone(1)), please feel free to let
us know, preferrably with a patch. :) There is a history that might
have left some of the documentation inconsistent.
Regards,
Jonathan
prev parent reply other threads:[~2010-08-20 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 7:17 git commands sandy2010
2010-08-20 7:32 ` Joshua Juran
2010-08-20 7:57 ` Matthieu Moy
2010-08-20 8:49 ` sandy2010
2010-08-22 10:41 ` Lin Mac
2010-08-22 21:19 ` David Aguilar
2010-08-20 7:51 ` Jonathan Nieder [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=20100820075111.GC24678@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jjuran@gmail.com \
--cc=sandeeptt@yahoo.com \
/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).