{"thread":{"id":"4047","subject":"Fetching a tree from a remote server","startedAt":"2006-05-04T00:41:52Z","lastAt":"2006-05-04T01:08:27Z","messageCount":3,"participants":["Daniel Barkalow","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"19486","messageId":"Pine.LNX.4.64.0605032026070.6713@iabervon.org","threadId":"4047","inReplyTo":null,"subject":"Fetching a tree from a remote server","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2006-05-04T00:41:52Z","receivedAt":"2006-05-04T00:41:52Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"Is there something to do the opposite of git clone -n? That is, I want to \nfill a directory with a treeish ref, and I don't care about any history or \nbookkeeping. I'm doing automated builds of things stored on a slow \nmachine, so I'd really benefit from not getting the history. As it is, \nit's only twice as fast as arch, when it really ought to be hundreds of \ntimes faster.\n\nAlso, git-archimport in 1.2.4 seems to leave master as the initial import, \nrather than either not having it or having it at the end, which is a bit \nconfusing.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"19488","messageId":"Pine.LNX.4.63.0605040247460.24675@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"4047","inReplyTo":"Pine.LNX.4.64.0605032026070.6713@iabervon.org","subject":"Re: Fetching a tree from a remote server","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2006-05-04T00:48:04Z","receivedAt":"2006-05-04T00:48:04Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 3 May 2006, Daniel Barkalow wrote:\n\n> Is there something to do the opposite of git clone -n? That is, I want to \n> fill a directory with a treeish ref, and I don't care about any history or \n> bookkeeping.\n\nIs git-tar-tree your friend or what?\n\nCiao,\nDscho\n"},{"id":"19491","messageId":"Pine.LNX.4.64.0605032054170.6713@iabervon.org","threadId":"4047","inReplyTo":"Pine.LNX.4.63.0605040247460.24675@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: Fetching a tree from a remote server","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2006-05-04T01:08:27Z","receivedAt":"2006-05-04T01:08:27Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Thu, 4 May 2006, Johannes Schindelin wrote:\n\n> Hi,\n> \n> On Wed, 3 May 2006, Daniel Barkalow wrote:\n> \n> > Is there something to do the opposite of git clone -n? That is, I want to \n> > fill a directory with a treeish ref, and I don't care about any history or \n> > bookkeeping.\n> \n> Is git-tar-tree your friend or what?\n\nThe problem is that I'm on the build machine, and the repository is on the \nremote server. I suppose I could do \"(ssh server \nGIT_DIR=/repo.git git-tar-tree HEAD) | tar -xf -\", but that's not quite \nthe most clear thing, and I'd have to split up the URLs. Also, it wouldn't \nwork with only git: access to the repository.\n\n(On the other hand, it does work for my actual application, I'm doing it \nfrom a Makefile, and it's blazingly fast, so I guess I'm set.)\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}