From: Jakub Narebski <jnareb@gmail.com>
To: 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 23:53:14 +0100 [thread overview]
Message-ID: <ejvvts$9eu$1@sea.gmane.org> (raw)
In-Reply-To: 45638212.8030501@freescale.com
Timur Tabi wrote:
> Johannes Schindelin wrote:
>> Try "git clone --depth 1 <url>". This will cut each ancestor chain after
>> one ancestor (IIRC).
>
> I think you mean git-clone.sh instead of git-clone. If I do the above command,
> I get:
>
> $ ./git clone --depth 1 git://127.0.0.1/temp/u-boot-83xx/
> Usage: /home/b04825/bin/git-clone [--template=<template_directory>]
> [--use-separate-remote] [--reference <reference-repo>] [--bare] [-l [-s]] [-q]
> [-u <upload-pack>] [--origin <name>] [-n] <repo> [<dir>]
>
> However, git-clone.sh is not quite working either. I had to run git-daemon on
> my machine, because git-clone.sh doesn't like the http protocol, and my firewall
> blocks everything but that. So I cloned a repo, started git-daemon, and I tried
> this:
>
> $ ./git-clone.sh --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.
>
> A regular git-clone of git://127.0.0.1/temp/u-boot-83xx works, so I think
> there's something wrong with git-clone.sh or my invocation thereof.
Erm, you have to compile git with "make bindir=$(pwd)" to run it from
working directory. Or just install it somewhere not over git, like
/usr/local/ or /home/local/.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-11-21 22:53 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 [this message]
2006-11-21 22:53 ` Johannes Schindelin
2006-11-21 23:12 ` Timur Tabi
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='ejvvts$9eu$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).