From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Tracking a repository for content instead of history
Date: Tue, 12 Dec 2006 14:04:51 +0100 [thread overview]
Message-ID: <elm993$rf1$1@sea.gmane.org> (raw)
In-Reply-To: 200612121235.09984.andyparkins@gmail.com
Andy Parkins wrote:
> For interests sake I'd like to track the kernel.org linux repository.
> However, I'm not that bothered about tracking the history - it's more that I
> like to have the latest kernel release lying around.
>
> Is there a way that I could just pull individual commits from a git
> repository? In particular - could I make a repository (obviously not a
> clone, because it wouldn't have all the history) that contained only the
> tagged commits from an upstream repository?
As of beta (in 'next') you can do 'shallow clone'm i.e. clone/fetch
only N commits depth history.
> 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.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-12 13:02 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 [this message]
2006-12-12 13:26 ` Andy Parkins
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='elm993$rf1$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).