From: Shawn Pearce <spearce@spearce.org>
To: Timur Tabi <timur@freescale.com>
Cc: 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 11:32:06 -0500 [thread overview]
Message-ID: <20061121163206.GA22006@spearce.org> (raw)
In-Reply-To: <45632957.5070205@freescale.com>
Timur Tabi <timur@freescale.com> wrote:
> Thomas Kolejka wrote:
>
> >Is it possible to do this with shallow clone?
>
> Maybe. How do you do a shallow clone? I tried "git clone" followed by
> "git-repack", and that helped a lot, but the result was still twice the
> size of a normal tarball. I don't see any "shallow" option to the clone
> command, and git-shallow-pack doesn't exist on my installation.
Twice the size of a normal tarball isn't too bad, considering that
you have the _complete_ history in the pack and yet the normal
tarball has no history at all.
Shallow clone is a development feature still being working on in
Junio's 'pu' branch of git.git. It has a few issues still to be
worked out so it hasn't been made part of one of the more stable
branches yet (like 'next', 'master', or 'maint').
--
next prev parent reply other threads:[~2006-11-21 16:33 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 [this message]
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
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=20061121163206.GA22006@spearce.org \
--to=spearce@spearce.org \
--cc=Thomas.Kolejka@gmx.at \
--cc=git@vger.kernel.org \
--cc=timur@freescale.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.