# git commands 7 messages from 2010-08-20 to 2010-08-22. Participants: sandy2010, Joshua Juran, Jonathan Nieder, Matthieu Moy, Lin Mac, David Aguilar. Thread: https://gitlist.dev/t/24799 ## sandy2010, 2010-08-20 07:17 Subject: git commands Message-ID: <1282288658094-5443370.post@n2.nabble.com> URL: https://gitlist.dev/e/1282288658094-5443370.post%40n2.nabble.com ``` 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? -- View this message in context: http://git.661346.n2.nabble.com/git-commands-tp5443370p5443370.html Sent from the git mailing list archive at Nabble.com. ``` ## Joshua Juran, 2010-08-20 07:32 Subject: Re: git commands Message-ID: <5F6739C3-B537-4694-BC63-F3F74962A47C@gmail.com> URL: https://gitlist.dev/e/5F6739C3-B537-4694-BC63-F3F74962A47C%40gmail.com In-Reply-To: <1282288658094-5443370.post@n2.nabble.com> ``` On Aug 20, 2010, at 12:17 AM, 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? They're the same command. You should use the first form to actually run the command and the hyphenated form for consulting the manual: git clone git://git.kernel.org/pub/scm/git/git.git man git-clone You may get speedier responses to easy questions on IRC, in #git. Cheers, Josh ``` ## Jonathan Nieder, 2010-08-20 07:51 Subject: Re: git commands Message-ID: <20100820075111.GC24678@burratino> URL: https://gitlist.dev/e/20100820075111.GC24678%40burratino 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 ``` ## Matthieu Moy, 2010-08-20 07:57 Subject: Re: git commands Message-ID: URL: https://gitlist.dev/e/vpq39u97m3l.fsf%40bauges.imag.fr In-Reply-To: <5F6739C3-B537-4694-BC63-F3F74962A47C@gmail.com> ``` Joshua Juran writes: > On Aug 20, 2010, at 12:17 AM, 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? > > They're the same command. Except that "git-clone" doesn't work with Git >= 1.6. If you ask the question, I suspect you have a rather old version of Git and you're a beginner. Git's user-friendlyness to newbies greatly improved over the last versions, so I'd suggest upgrading. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ ``` ## sandy2010, 2010-08-20 08:49 Subject: Re: git commands Message-ID: <1282294163263-5443609.post@n2.nabble.com> URL: https://gitlist.dev/e/1282294163263-5443609.post%40n2.nabble.com In-Reply-To: ``` Yeah.. Actually, we were using git-15.6 and the command we used was 'git-clone'. Later, I upgraded to git-1.7.1 and I found that in the installation directory, there was only 4 binaries including git. I was wondering were are the rest commands like git-clone, etc? Hence, I asked this question. Thanks all for your response. Correct way is to use 'git clone'. -- View this message in context: http://git.661346.n2.nabble.com/git-commands-tp5443370p5443609.html Sent from the git mailing list archive at Nabble.com. ``` ## Lin Mac, 2010-08-22 10:41 Subject: Re: git commands Message-ID: URL: https://gitlist.dev/e/AANLkTimRpwLZHve_cAY0JxLGKC4202i-V_Soq%3Dm1_JsY%40mail.gmail.com In-Reply-To: <1282294163263-5443609.post@n2.nabble.com> ``` Hi, 2010/8/20 sandy2010 : > Yeah.. Actually, we were using git-15.6 and the command we used was > 'git-clone'. Later, I upgraded to git-1.7.1 and I found that in the > installation directory, there was only 4 binaries including git. I was > wondering were are the rest commands like git-clone, etc? Hence, I asked > this question. I have the same question regarding the installation here. I'm trying to upgrade from v1.5.x to the newest. But found that there are only a few files installed. Where are the rest? Should I uninstall the old version before I install? And is there any issues for the newer version works in respository made by v1.5.x, like git-svn? Best Regards, Mac Lin. ``` ## David Aguilar, 2010-08-22 21:19 Subject: Re: git commands Message-ID: <20100822211921.GA27048@gmail.com> URL: https://gitlist.dev/e/20100822211921.GA27048%40gmail.com In-Reply-To: ``` On Sun, Aug 22, 2010 at 06:41:35PM +0800, Lin Mac wrote: > Hi, > > 2010/8/20 sandy2010 : > > Yeah.. Actually, we were using git-15.6 and the command we used was > > 'git-clone'. Later, I upgraded to git-1.7.1 and I found that in the > > installation directory, there was only 4 binaries including git. I was > > wondering were are the rest commands like git-clone, etc? Hence, I asked > > this question. > I have the same question regarding the installation here. I'm trying > to upgrade from v1.5.x to the newest. But found that there are only a > few files installed. Where are the rest? Should I uninstall the old > version before I install? And is there any issues for the newer > version works in respository made by v1.5.x, like git-svn? > > Best Regards, > Mac Lin. Uninstall the old one and install the new one. All the same commands are there, they're just organized nicer so that they don't have to necessarily live in your $PATH. The old version provided commands like 'git-clone' in /usr/bin. You cannot use them like that anymore. These days we say 'git clone' (no dashes). Here's a blurb from http://lkml.org/lkml/2008/8/17/174 GIT v1.6.0 Release Notes ======================== User visible changes -------------------- With the default Makefile settings, most of the programs are now installed outside your $PATH, except for "git", "gitk" and some server side programs that need to be accessible for technical reasons. Invoking a git subcommand as "git-xyzzy" from the command line has been deprecated since early 2006 (and officially announced in 1.5.4 release notes); use of them from your scripts after adding output from "git --exec-path" to the $PATH is still supported in this release, but users are again strongly encouraged to adjust their scripts to use "git xyzzy" form, as we will stop installing "git-xyzzy" hardlinks for built-in commands in later releases. -- David ```