From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: Tracking a repository for content instead of history
Date: Tue, 12 Dec 2006 13:26:22 +0000 [thread overview]
Message-ID: <200612121326.24508.andyparkins@gmail.com> (raw)
In-Reply-To: <elm993$rf1$1@sea.gmane.org>
On Tuesday 2006 December 12 13:04, Jakub Narebski wrote:
> > Is it even sensible to want that? It strikes me that it's possible that
> > there isn't that much space/bandwidth saving to be made. Should I just
> > clone the repository and shut up? :-)
>
> I've had similar idea: search for "sparse clone" keyword. But no code.
While the functionality might not be built into git in terms of clone, would
there be a way to pull a particular commit from another repository?
The way I would do it given nothing else is to simply extract snapshots into a
working directory; and create a repository from scratch. I was just
wondering if a method existed that could reduce the size of the download.
I think the best way is going to be to use the patches published at kernel.org
and apply them one at a time with git-apply.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
next prev parent reply other threads:[~2006-12-12 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 12:35 Tracking a repository for content instead of history Andy Parkins
2006-12-12 13:04 ` Jakub Narebski
2006-12-12 13:26 ` Andy Parkins [this message]
2006-12-12 14:28 ` Johannes Schindelin
2006-12-12 15:38 ` Andy Parkins
2006-12-12 16:24 ` Johannes Schindelin
2006-12-12 16:35 ` Johannes Schindelin
2006-12-12 21:46 ` Nguyen Thai Ngoc Duy
2006-12-12 21:48 ` Nguyen Thai Ngoc Duy
2006-12-12 22:25 ` 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=200612121326.24508.andyparkins@gmail.com \
--to=andyparkins@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).