From: Timur Tabi <timur@freescale.com>
To: Shawn Pearce <spearce@spearce.org>
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 10:52:22 -0600 [thread overview]
Message-ID: <45632EC6.5030902@freescale.com> (raw)
In-Reply-To: <20061121163206.GA22006@spearce.org>
Shawn Pearce wrote:
> 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.
That is true. However, for the particular project I'm working on, double the
size is not really acceptable.
My goal is to provide a source tree that is "git enabled", so that user can use
git command to fetch, apply, and create patches. Currently, we're just handing
out tarballs, so we want to move people to the 21st century.
> 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').
Well, until it's available on an official git release, it doesn't help me.
--
Timur Tabi
next prev parent reply other threads:[~2006-11-21 16:52 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 [this message]
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=45632EC6.5030902@freescale.com \
--to=timur@freescale.com \
--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).