On Sun, Mar 25, 2012 at 05:12:57AM -0700, Whitehorse06 wrote: [...] > git clone -u /var/chroot/home/content/85/91334343/git/Readme.txt > myHostAlias > Cloning into myHostAlias... > /var/chroot/home/content/85/91334343/git/Readme.txt '/home/rams/ > domain/git/test/myHostAlias': 1: /var/chroot/home/content/85/91334343/ > git/Readme.txt: not found > fatal: The remote end hung up unexpectedly > > > I am struck. What is causing the problem?
Git is not Subversion, it's a DVCS so you can't just fetch one single file, instead, you have to *clone* (that's why it's called `git clone` after all) the whole repository (but see below). Consequently, you have to use the path to a repository with `git clone`. Technically, `git clone` can do what's called a "shallow clone", that is, it's able to fetch not the whole history but just the specified number of commits from a given remote branch and all associated objects, so you can kind of achieve what `svn checkout` can yield when run with the URL of a root directory of a project. But if you intend to do any serious work against a repository, shallow cloning is not a recommended way to go, it's intended for cases when you just want to fetch a source tree for the purpose of building it or something like this. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to firstname.lastname@example.org. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.