{"thread":{"id":"43250","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","startedAt":"2006-11-15T22:11:57Z","lastAt":"2006-11-21T23:22:41Z","messageCount":19,"participants":["Timur Tabi","Shawn Pearce","Thomas Kolejka","Jakub Narebski","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"296583","messageId":"455B90AD.3060707@freescale.com","threadId":"43250","inReplyTo":null,"subject":"Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Timur Tabi","fromEmail":"timur@freescale.com","sentAt":"2006-11-15T22:11:57Z","receivedAt":"2006-11-15T22:11:57Z","isPatch":false,"sender":{"key":"timur@freescale.com","avatar":null},"body":"After doing a \"make mrproper\" in my Linux git tree, the result is still 1.1GB \nof files. Compare that with just the tarball, which is just one-forth the size.\n\nIs there a way to \"trim away\" old commits from the repository, so that it just \ndoesn't take up that much space? I don't care about any commits made in 2005. \n As long as I can still do \"git pull\" from the source repo to update mine, \nthat's good enough.\n\n-- \nTimur Tabi\n"},{"id":"297376","messageId":"20061115221616.GD24861@spearce.org","threadId":"43250","inReplyTo":"455B90AD.3060707@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2006-11-15T22:16:16Z","receivedAt":"2006-11-15T22:16:16Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Timur Tabi wrote:\n> After doing a \"make mrproper\" in my Linux git tree, the result is still \n> 1.1GB of files. Compare that with just the tarball, which is just \n> one-forth the size.\n> \n> Is there a way to \"trim away\" old commits from the repository, so that it \n> just doesn't take up that much space? I don't care about any commits made \n> in 2005. As long as I can still do \"git pull\" from the source repo to \n> update mine, that's good enough.\n\nNo. However...\n\nHave you tried \"git repack -a -d\" to repack the loose objects into\na pack file? Doing this every so often should reduce your disk\nspace consumed by a HUGE amount.\n\n-- \n"},{"id":"297526","messageId":"455B9411.4090708@freescale.com","threadId":"43250","inReplyTo":"20061115221616.GD24861@spearce.org","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Timur Tabi","fromEmail":"timur@freescale.com","sentAt":"2006-11-15T22:26:25Z","receivedAt":"2006-11-15T22:26:25Z","isPatch":false,"sender":{"key":"timur@freescale.com","avatar":null},"body":"Shawn Pearce wrote:\n\n> Have you tried \"git repack -a -d\" to repack the loose objects into\n> a pack file? Doing this every so often should reduce your disk\n> space consumed by a HUGE amount.\n\nWoah! It shrunk that bad boy down to 420M! That should do it, thanks!\n\nI wonder why the powerpc tree shrank so much. Do you think the maintainer \njust needs to run git-repack on his tree?\n\n-- \nTimur Tabi\n"},{"id":"296459","messageId":"20061115223300.GF24861@spearce.org","threadId":"43250","inReplyTo":"455B9411.4090708@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2006-11-15T22:33:00Z","receivedAt":"2006-11-15T22:33:00Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Timur Tabi wrote:\n> Shawn Pearce wrote:\n> \n> >Have you tried \"git repack -a -d\" to repack the loose objects into\n> >a pack file? Doing this every so often should reduce your disk\n> >space consumed by a HUGE amount.\n> \n> Woah! It shrunk that bad boy down to 420M! That should do it, thanks!\n> \n> I wonder why the powerpc tree shrank so much. Do you think the maintainer \n> just needs to run git-repack on his tree?\n\nPossible, yes.\n\nHowever published repositories don't tend to repack as often as\nit makes things harder for people who clone/fetch over HTTP rather\nthan the native git protocol.\n\nThe reason is that HTTP can fetch individual loose objects that\nyou don't have yet, but if the object is only available in a pack\nfile then you need to fetch the entire pack file. But you might\nalready have most of that pack file, so now you are downloading\nlots of data you already have. :-(\n\n-- \n"},{"id":"294571","messageId":"20061117103611.183640@gmx.net","threadId":"43250","inReplyTo":"455B90AD.3060707@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Thomas Kolejka","fromEmail":"thomas.kolejka@gmx.at","sentAt":"2006-11-17T10:36:11Z","receivedAt":"2006-11-17T10:36:11Z","isPatch":false,"sender":{"key":"thomas.kolejka@gmx.at","avatar":null},"body":"\n-------- Original-Nachricht --------\nDatum: Wed, 15 Nov 2006 16:11:57 -0600\nVon: Timur Tabi \nAn: git@vger.kernel.org\nBetreff: Is there a way to trim old SHAs from a git tree (so it\\'s not so large)?\n\n> After doing a \"make mrproper\" in my Linux git tree, the result is still\n> 1.1GB \n> of files. Compare that with just the tarball, which is just one-forth the\n> size.\n> \n> Is there a way to \"trim away\" old commits from the repository, so that it\n> just \n> doesn't take up that much space? I don't care about any commits made in\n> 2005. \n> As long as I can still do \"git pull\" from the source repo to update\n> mine, \n> that's good enough.\n> \n> -- \n> Timur Tabi\n> Linux Kernel Developer @ Freescale\n\nIs it possible to do this with shallow clone? \nShallow clone the local repository my.git (which should be trimmed) starting from the last needed commit to a new local repository my_trimmed.git. And then remove my.git (with something like rm -rf my.git) and rename my_trimmed.git to my.git?\n\nThomas\n-- \nDer GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! \n"},{"id":"296137","messageId":"45632957.5070205@freescale.com","threadId":"43250","inReplyTo":"20061117103611.183640@gmx.net","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Timur Tabi","fromEmail":"timur@freescale.com","sentAt":"2006-11-21T16:29:11Z","receivedAt":"2006-11-21T16:29:11Z","isPatch":false,"sender":{"key":"timur@freescale.com","avatar":null},"body":"Thomas Kolejka wrote:\n\n> Is it possible to do this with shallow clone? \n\nMaybe. How do you do a shallow clone? I tried \"git clone\" followed by \n\"git-repack\", and that helped a lot, but the result was still twice the size of \na normal tarball. I don't see any \"shallow\" option to the clone command, and \ngit-shallow-pack doesn't exist on my installation.\n\n-- \nTimur Tabi\n"},{"id":"295651","messageId":"20061121163206.GA22006@spearce.org","threadId":"43250","inReplyTo":"45632957.5070205@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2006-11-21T16:32:06Z","receivedAt":"2006-11-21T16:32:06Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Timur Tabi wrote:\n> Thomas Kolejka wrote:\n> \n> >Is it possible to do this with shallow clone? \n> \n> Maybe. How do you do a shallow clone? I tried \"git clone\" followed by \n> \"git-repack\", and that helped a lot, but the result was still twice the \n> size of a normal tarball. I don't see any \"shallow\" option to the clone \n> command, and git-shallow-pack doesn't exist on my installation.\n\nTwice the size of a normal tarball isn't too bad, considering that\nyou have the _complete_ history in the pack and yet the normal\ntarball has no history at all.\n\nShallow clone is a development feature still being working on in\nJunio's 'pu' branch of git.git. It has a few issues still to be\nworked out so it hasn't been made part of one of the more stable\nbranches yet (like 'next', 'master', or 'maint').\n\n-- \n"},{"id":"298063","messageId":"45632EC6.5030902@freescale.com","threadId":"43250","inReplyTo":"20061121163206.GA22006@spearce.org","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Timur Tabi","fromEmail":"timur@freescale.com","sentAt":"2006-11-21T16:52:22Z","receivedAt":"2006-11-21T16:52:22Z","isPatch":false,"sender":{"key":"timur@freescale.com","avatar":null},"body":"Shawn Pearce wrote:\n\n> Twice the size of a normal tarball isn't too bad, considering that\n> you have the _complete_ history in the pack and yet the normal\n> tarball has no history at all.\n\nThat is true. However, for the particular project I'm working on, double the \nsize is not really acceptable.\n\nMy goal is to provide a source tree that is \"git enabled\", so that user can use \ngit command to fetch, apply, and create patches. Currently, we're just handing \nout tarballs, so we want to move people to the 21st century.\n\n> Shallow clone is a development feature still being working on in\n> Junio's 'pu' branch of git.git. It has a few issues still to be\n> worked out so it hasn't been made part of one of the more stable\n> branches yet (like 'next', 'master', or 'maint').\n\nWell, until it's available on an official git release, it doesn't help me.\n\n-- \nTimur Tabi\n"},{"id":"294317","messageId":"20061121165656.GC22006@spearce.org","threadId":"43250","inReplyTo":"45632EC6.5030902@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2006-11-21T16:56:56Z","receivedAt":"2006-11-21T16:56:56Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Timur Tabi wrote:\n> >Shallow clone is a development feature still being working on in\n> >Junio's 'pu' branch of git.git. It has a few issues still to be\n> >worked out so it hasn't been made part of one of the more stable\n> >branches yet (like 'next', 'master', or 'maint').\n> \n> Well, until it's available on an official git release, it doesn't help me.\n\nOne of the reasons its hanging out in 'pu' still is that there is\na lack of people who are interested in the feature, and thus not\nenough people are testing it. Perhaps you might be able to lend\na hand in that regard?\n\n-- \n"},{"id":"297795","messageId":"Pine.LNX.4.63.0611211756510.13772@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"43250","inReplyTo":"45632EC6.5030902@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2006-11-21T16:57:33Z","receivedAt":"2006-11-21T16:57:33Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 21 Nov 2006, Timur Tabi wrote:\n\n> Shawn Pearce wrote:\n> \n> > Shallow clone is a development feature still being working on in\n> > Junio's 'pu' branch of git.git. It has a few issues still to be\n> > worked out so it hasn't been made part of one of the more stable\n> > branches yet (like 'next', 'master', or 'maint').\n> \n> Well, until it's available on an official git release, it doesn't help \n> me.\n\nWell, if you help it, it will be available on an official git release \nsoon!\n\nCiao,\nDscho\n"},{"id":"295195","messageId":"456330CD.9080503@freescale.com","threadId":"43250","inReplyTo":"20061121165656.GC22006@spearce.org","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Timur Tabi","fromEmail":"timur@freescale.com","sentAt":"2006-11-21T17:01:01Z","receivedAt":"2006-11-21T17:01:01Z","isPatch":false,"sender":{"key":"timur@freescale.com","avatar":null},"body":"Shawn Pearce wrote:\n> Timur Tabi wrote:\n>>> Shallow clone is a development feature still being working on in\n>>> Junio's 'pu' branch of git.git. It has a few issues still to be\n>>> worked out so it hasn't been made part of one of the more stable\n>>> branches yet (like 'next', 'master', or 'maint').\n>> Well, until it's available on an official git release, it doesn't help me.\n> \n> One of the reasons its hanging out in 'pu' still is that there is\n> a lack of people who are interested in the feature, and thus not\n> enough people are testing it. Perhaps you might be able to lend\n> a hand in that regard?\n\nSure, I can do that! Can you give me some pointers? I've never done \ndevelopment on git itself, so I don't know Junio or his pu (sorry, I couldn't \nresist :-)).\n\n-- \nTimur Tabi\n"},{"id":"296616","messageId":"20061121183941.GB22283@spearce.org","threadId":"43250","inReplyTo":"456330CD.9080503@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2006-11-21T18:39:41Z","receivedAt":"2006-11-21T18:39:41Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Timur Tabi wrote:\n> Shawn Pearce wrote:\n> >Timur Tabi wrote:\n> >>>Shallow clone is a development feature still being working on in\n> >>>Junio's 'pu' branch of git.git. It has a few issues still to be\n> >>>worked out so it hasn't been made part of one of the more stable\n> >>>branches yet (like 'next', 'master', or 'maint').\n> >>Well, until it's available on an official git release, it doesn't help me.\n> >\n> >One of the reasons its hanging out in 'pu' still is that there is\n> >a lack of people who are interested in the feature, and thus not\n> >enough people are testing it. Perhaps you might be able to lend\n> >a hand in that regard?\n> \n> Sure, I can do that! Can you give me some pointers? I've never done \n> development on git itself, so I don't know Junio or his pu (sorry, I \n> couldn't resist :-)).\n\nJunio C Hamano is the Git maintainer. His published Git repository\nis here:\n\n\thttp://www.kernel.org/pub/scm/git/git.git/\n\nthough it oddly has pack files from Jun 2006 in the wrong directory.\nWeird. Anyway...\n\nIf you clone from that URL, or better though the native Git protocol:\n\n\tgit://www.kernel.org/pub/scm/git/git.git\n\nyou will get a branch called `pu`, which is the set of \"Proposed\nUpdates\" to Git that Junio and others are currently working on.\nYou can then checkout a branch off that, and build it:\n\n\tgit checkout -b pu-build pu\n\tmake\n\nfinally you can either run from that directory (see INSTALL file)\nor you can install the binary somewhere else. We don't really\nrecommend using `pu` for production level work, so make sure you\nhave a backup of any repository you run it on. :)\n\n-- \n"},{"id":"296980","messageId":"45637457.1010505@freescale.com","threadId":"43250","inReplyTo":"20061121183941.GB22283@spearce.org","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Timur Tabi","fromEmail":"timur@freescale.com","sentAt":"2006-11-21T21:49:11Z","receivedAt":"2006-11-21T21:49:11Z","isPatch":false,"sender":{"key":"timur@freescale.com","avatar":null},"body":"Shawn Pearce wrote:\n\n> finally you can either run from that directory (see INSTALL file)\n> or you can install the binary somewhere else. We don't really\n> recommend using `pu` for production level work, so make sure you\n> have a backup of any repository you run it on. :)\n\nSo how do I make a shallow clone? I've set it all up, but there is no \ngit-shallow-clone command, and git help clone doesn't have anything either.\n\n\n-- \nTimur Tabi\n"},{"id":"298368","messageId":"Pine.LNX.4.63.0611212306060.26827@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"43250","inReplyTo":"45637457.1010505@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2006-11-21T22:06:57Z","receivedAt":"2006-11-21T22:06:57Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 21 Nov 2006, Timur Tabi wrote:\n\n> Shawn Pearce wrote:\n> \n> > finally you can either run from that directory (see INSTALL file)\n> > or you can install the binary somewhere else. We don't really\n> > recommend using `pu` for production level work, so make sure you\n> > have a backup of any repository you run it on. :)\n> \n> So how do I make a shallow clone? I've set it all up, but there is no\n> git-shallow-clone command, and git help clone doesn't have anything either.\n\nTry \"git clone --depth 1 \". This will cut each ancestor chain after \none ancestor (IIRC).\n\nCiao,\nDscho\n"},{"id":"296497","messageId":"45638212.8030501@freescale.com","threadId":"43250","inReplyTo":"Pine.LNX.4.63.0611212306060.26827@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Timur Tabi","fromEmail":"timur@freescale.com","sentAt":"2006-11-21T22:47:46Z","receivedAt":"2006-11-21T22:47:46Z","isPatch":false,"sender":{"key":"timur@freescale.com","avatar":null},"body":"Johannes Schindelin wrote:\n> Hi,\n> \n> On Tue, 21 Nov 2006, Timur Tabi wrote:\n> \n>> Shawn Pearce wrote:\n>>\n>>> finally you can either run from that directory (see INSTALL file)\n>>> or you can install the binary somewhere else. We don't really\n>>> recommend using `pu` for production level work, so make sure you\n>>> have a backup of any repository you run it on. :)\n>> So how do I make a shallow clone? I've set it all up, but there is no\n>> git-shallow-clone command, and git help clone doesn't have anything either.\n> \n> Try \"git clone --depth 1 \". This will cut each ancestor chain after \n> one ancestor (IIRC).\n\nI think you mean git-clone.sh instead of git-clone. If I do the above command, \nI get:\n\n$ ./git clone --depth 1 git://127.0.0.1/temp/u-boot-83xx/\nUsage: /home/b04825/bin/git-clone [--template=] \n[--use-separate-remote] [--reference ] [--bare] [-l [-s]] [-q] \n[-u ] [--origin ] [-n] []\n\nHowever, git-clone.sh is not quite working either. I had to run git-daemon on \nmy machine, because git-clone.sh doesn't like the http protocol, and my firewall \nblocks everything but that. So I cloned a repo, started git-daemon, and I tried \nthis:\n\n$ ./git-clone.sh --depth 1 git://127.0.0.1/temp/u-boot-83xx\nusage: git-fetch-pack [--all] [-q] [-v] [-k] [--thin] [--exec=upload-pack] \n[host:]directory ...\nfetch-pack from 'git://127.0.0.1/temp/u-boot-83xx/' failed.\n\nA regular git-clone of git://127.0.0.1/temp/u-boot-83xx works, so I think \nthere's something wrong with git-clone.sh or my invocation thereof.\n\n-- \nTimur Tabi\n"},{"id":"298233","messageId":"ejvvts$9eu$1@sea.gmane.org","threadId":"43250","inReplyTo":"45638212.8030501@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-11-21T22:53:14Z","receivedAt":"2006-11-21T22:53:14Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Timur Tabi wrote:\n\n> Johannes Schindelin wrote:\n\n>> Try \"git clone --depth 1 \". This will cut each ancestor chain after \n>> one ancestor (IIRC).\n> \n> I think you mean git-clone.sh instead of git-clone. If I do the above command, \n> I get:\n> \n> $ ./git clone --depth 1 git://127.0.0.1/temp/u-boot-83xx/\n> Usage: /home/b04825/bin/git-clone [--template=] \n> [--use-separate-remote] [--reference ] [--bare] [-l [-s]] [-q] \n> [-u ] [--origin ] [-n] []\n> \n> However, git-clone.sh is not quite working either. I had to run git-daemon on \n> my machine, because git-clone.sh doesn't like the http protocol, and my firewall \n> blocks everything but that. So I cloned a repo, started git-daemon, and I tried \n> this:\n> \n> $ ./git-clone.sh --depth 1 git://127.0.0.1/temp/u-boot-83xx\n> usage: git-fetch-pack [--all] [-q] [-v] [-k] [--thin] [--exec=upload-pack] \n> [host:]directory ...\n> fetch-pack from 'git://127.0.0.1/temp/u-boot-83xx/' failed.\n> \n> A regular git-clone of git://127.0.0.1/temp/u-boot-83xx works, so I think \n> there's something wrong with git-clone.sh or my invocation thereof.\n\nErm, you have to compile git with \"make bindir=$(pwd)\" to run it from\nworking directory. Or just install it somewhere not over git, like\n/usr/local/ or /home/local/.\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n\n"},{"id":"297600","messageId":"Pine.LNX.4.63.0611212349440.26827@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"43250","inReplyTo":"45638212.8030501@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2006-11-21T22:53:31Z","receivedAt":"2006-11-21T22:53:31Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 21 Nov 2006, Timur Tabi wrote:\n\n> I think you mean git-clone.sh instead of git-clone.\n\nNo. If \"git clone\" does not work for you, the compilation failed. Do you \nrun git in-place? Then you _have_ to set\n\n\tbindir=$(pwd)\n\nin config.mak. Otherwise, the git wrapper (you wrote \"git-clone\", but then \nyou used \"git clone\") will look in $(HOME)/bin for your executables, and I \nbet that you have the other (official) git installed there.\n\n> However, git-clone.sh is not quite working either. I had to run \n> git-daemon on my machine, because git-clone.sh doesn't like the http \n> protocol, and my firewall blocks everything but that.\n\nFor now, shallow clones only work with the git protocol, i.e. via \ngit-daemon and ssh.\n\nHth,\n"},{"id":"294137","messageId":"456387D5.9080407@freescale.com","threadId":"43250","inReplyTo":"Pine.LNX.4.63.0611212349440.26827@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Timur Tabi","fromEmail":"timur@freescale.com","sentAt":"2006-11-21T23:12:21Z","receivedAt":"2006-11-21T23:12:21Z","isPatch":false,"sender":{"key":"timur@freescale.com","avatar":null},"body":"Johannes Schindelin wrote:\n> Hi,\n> \n> On Tue, 21 Nov 2006, Timur Tabi wrote:\n> \n>> I think you mean git-clone.sh instead of git-clone.\n> \n> No. If \"git clone\" does not work for you, the compilation failed. Do you \n> run git in-place? Then you _have_ to set\n> \n> \tbindir=$(pwd)\n> \n> in config.mak.\n\nWhen I tried that, make spits out this:\n\nGIT_VERSION = 1.4.4.ge1173-dirty\n * new build flags or prefix\n(cd perl && /usr/bin/perl Makefile.PL \\\n PREFIX='/home/b04825')\nWriting Makefile for Git\n\nSo I tried this:\n\nmake configure\n./configure --prefix=$PWD\nmake\n\nand got this:\n\n * new build flags or prefix\n(cd perl && /usr/bin/perl Makefile.PL \\\n PREFIX='/temp/git')\nWriting Makefile for Git\n\nwhich is better, but git-clone still doesn't work:\n\n$ ./git clone --depth 1 git://127.0.0.1/temp/u-boot-83xx\nFailed to run command 'clone': Success\n\n$ ./git-clone --depth 1 git://127.0.0.1/temp/u-boot-83xx\nusage: git-fetch-pack [--all] [-q] [-v] [-k] [--thin] [--exec=upload-pack] \n[host:]directory ...\nfetch-pack from 'git://127.0.0.1/temp/u-boot-83xx' failed.\n\nIn both of these cases, the git-daemon process doesn't log anything.\n\nI even tried \"export GIT_DIR=$PWD\", but that didn't do anything.\n\n-- \nTimur Tabi\n"},{"id":"294665","messageId":"ek01l3$ihf$1@sea.gmane.org","threadId":"43250","inReplyTo":"456387D5.9080407@freescale.com","subject":"Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-11-21T23:22:41Z","receivedAt":"2006-11-21T23:22:41Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Timur Tabi wrote:\n\n> make configure\n> ./configure --prefix=$PWD\n> make\n\nmake configure\n./configure --prefix=$PWD --bindir=$PWD\nmake\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n\n"}]}