{"thread":{"id":"13023","subject":"question about git and remote repositories","startedAt":"2008-04-08T19:08:57Z","lastAt":"2008-04-08T20:24:03Z","messageCount":3,"participants":["Ittay Dror","Michele Ballabio","Avery Pennarun"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"73867","messageId":"47FBC2C9.6060702@tikalk.com","threadId":"13023","inReplyTo":null,"subject":"question about git and remote repositories","fromName":"Ittay Dror","fromEmail":"ittayd@tikalk.com","sentAt":"2008-04-08T19:08:57Z","receivedAt":"2008-04-08T19:08:57Z","isPatch":false,"sender":{"key":"ittayd@tikalk.com","avatar":null},"body":"Hi,\n\nIf I want to start working on a project that uses git (and I want to use \ngit also), I first need to clone the project's repo. That is very slow \n(using the git:// protocol). Are there alternatives? For example, as far \nas I understand, if all I want is to get the latest commit in HEAD, \nbranch from it and start working, then all git really needs to have is \nall objects referenced from that commit (commit, trees, blobs) and \nthat's it, right? (as long as I don't expect to see full log of past \noperations)\n\nThanks,\nIttay\n\n-- \nIttay Dror \nTikal \nTikal Project \n"},{"id":"73870","messageId":"200804082208.26220.barra_cuda@katamail.com","threadId":"13023","inReplyTo":"47FBC2C9.6060702@tikalk.com","subject":"Re: question about git and remote repositories","fromName":"Michele Ballabio","fromEmail":"barra_cuda@katamail.com","sentAt":"2008-04-08T20:08:25Z","receivedAt":"2008-04-08T20:08:25Z","isPatch":false,"sender":{"key":"barra_cuda@katamail.com","avatar":"https://avatars.githubusercontent.com/u/16371673?v=4"},"body":"On Tuesday 08 April 2008, Ittay Dror wrote:\n> If I want to start working on a project that uses git (and I want to use \n> git also), I first need to clone the project's repo. That is very slow \n> (using the git:// protocol). Are there alternatives? For example, as far \n> as I understand, if all I want is to get the latest commit in HEAD, \n> branch from it and start working, then all git really needs to have is \n> all objects referenced from that commit (commit, trees, blobs) and \n> that's it, right? (as long as I don't expect to see full log of past \n> operations)\n\nIn git terms, that is called a \"shallow clone\". For example:\n\ngit clone --depth 5 git://site.com/repo.git\n\nwould clone all the heads of repo.git along with their 5 most\nrecent commits.\n\nYou can make history deeper with\n\ngit-fetch --depth 20 git://site.com/repo.git branch\n\nSee the glossary, technical/shallow.txt, git-clone and git-fetch\nman pages.\n"},{"id":"73872","messageId":"32541b130804081324q7555aff5ia123512db014e24f@mail.gmail.com","threadId":"13023","inReplyTo":"47FBC2C9.6060702@tikalk.com","subject":"Re: question about git and remote repositories","fromName":"Avery Pennarun","fromEmail":"apenwarr@gmail.com","sentAt":"2008-04-08T20:24:03Z","receivedAt":"2008-04-08T20:24:03Z","isPatch":false,"sender":{"key":"apenwarr@gmail.com","avatar":"https://avatars.githubusercontent.com/u/20592?v=4"},"body":"On Tue, Apr 8, 2008 at 3:08 PM, Ittay Dror wrote:\n> For example, as far as\n> I understand, if all I want is to get the latest commit in HEAD, branch from\n> it and start working, then all git really needs to have is all objects\n> referenced from that commit (commit, trees, blobs) and that's it, right? (as\n> long as I don't expect to see full log of past operations)\n\nIt can be quite addictive to have the entire revision history of the\nentire project sitting locally on your disk. Once you've tried it,\nit's hard to go back. :)\n\nBut if you still want only the last few revisions, try using the\n--depth option to git-clone.\n\nHave fun,\n\nAvery\n"}]}