From: Timur Tabi <timur@freescale.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Shawn Pearce <spearce@spearce.org>,
Thomas Kolejka <Thomas.Kolejka@gmx.at>,
git@vger.kernel.org
Subject: Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?
Date: Tue, 21 Nov 2006 17:12:21 -0600 [thread overview]
Message-ID: <456387D5.9080407@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0611212349440.26827@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Tue, 21 Nov 2006, Timur Tabi wrote:
>
>> I think you mean git-clone.sh instead of git-clone.
>
> No. If "git clone" does not work for you, the compilation failed. Do you
> run git in-place? Then you _have_ to set
>
> bindir=$(pwd)
>
> in config.mak.
When I tried that, make spits out this:
GIT_VERSION = 1.4.4.ge1173-dirty
* new build flags or prefix
(cd perl && /usr/bin/perl Makefile.PL \
PREFIX='/home/b04825')
Writing Makefile for Git
So I tried this:
make configure
./configure --prefix=$PWD
make
and got this:
* new build flags or prefix
(cd perl && /usr/bin/perl Makefile.PL \
PREFIX='/temp/git')
Writing Makefile for Git
which is better, but git-clone still doesn't work:
$ ./git clone --depth 1 git://127.0.0.1/temp/u-boot-83xx
Failed to run command 'clone': Success
$ ./git-clone --depth 1 git://127.0.0.1/temp/u-boot-83xx
usage: git-fetch-pack [--all] [-q] [-v] [-k] [--thin] [--exec=upload-pack]
[host:]directory <refs>...
fetch-pack from 'git://127.0.0.1/temp/u-boot-83xx' failed.
In both of these cases, the git-daemon process doesn't log anything.
I even tried "export GIT_DIR=$PWD", but that didn't do anything.
--
Timur Tabi
next prev parent reply other threads:[~2006-11-21 23:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 22:11 Is there a way to trim old SHAs from a git tree (so it's not so large)? Timur Tabi
2006-11-15 22:16 ` Shawn Pearce
2006-11-15 22:26 ` Timur Tabi
2006-11-15 22:33 ` Shawn Pearce
2006-11-17 10:36 ` Thomas Kolejka
2006-11-21 16:29 ` Timur Tabi
2006-11-21 16:32 ` Shawn Pearce
2006-11-21 16:52 ` Timur Tabi
2006-11-21 16:56 ` Shawn Pearce
2006-11-21 17:01 ` Timur Tabi
2006-11-21 18:39 ` Shawn Pearce
2006-11-21 21:49 ` Timur Tabi
2006-11-21 22:06 ` Johannes Schindelin
2006-11-21 22:47 ` Timur Tabi
2006-11-21 22:53 ` Jakub Narebski
2006-11-21 22:53 ` Johannes Schindelin
2006-11-21 23:12 ` Timur Tabi [this message]
2006-11-21 23:22 ` Jakub Narebski
2006-11-21 16:57 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=456387D5.9080407@freescale.com \
--to=timur@freescale.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Thomas.Kolejka@gmx.at \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).