From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "eric miao" <eric.y.miao@gmail.com>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Will git have a baseline feature or something alike?
Date: Sat, 1 Mar 2008 21:29:04 +0700 [thread overview]
Message-ID: <fcaeb9bf0803010629v4894ad92ief4d5ef4257723e@mail.gmail.com> (raw)
In-Reply-To: <f17812d70803010610o39cdf327x995c9e2e75a9edba@mail.gmail.com>
On Sat, Mar 1, 2008 at 9:10 PM, eric miao <eric.y.miao@gmail.com> wrote:
> On Fri, Feb 29, 2008 at 9:21 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> > "eric miao" <eric.y.miao@gmail.com> writes:
> >
> > > I kept a mirror of
> > >
> > > http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > >
> > > by a crontab task fetching the updated commits at midnight everyday.
> > >
> > > Yet I found the repository now grows to be 1.2G without checking out
> > > anything. The checked out working tree of this is about 1.5G.
> >
> > Did you (re)packed this repository, running "git gc", or "git repack"?
> > Currently git either downloads small packs, or loose objects; it needs
> > to repack to make repository size smaller.
> >
> > BTW. the largest git repository is 1.6G OpenOffice.org conversion,
> > with > 2G checkout, and some large binary files under version
> > control. Mozilla and GCC, other large repos, got under 0.5G IIRC.
> > So kernel should be quite smaller.
> >
> >
> > > I tried "git prune" and "git repack" but it still remains so large. The
> > > trend of the kernel is still going to be enlarged. Thus I'm thinking
> > > of the possibility of a baseline feature. One can totally forget about
> > > the history before that baseline, and start the development there
> > > after.
> >
> > There is so called "shallow clone" feature, which allows to clone only
> > part of history. Currently it dupports only --depth, i.e. number of
> > commits from tips; it could I guess support providing tag as
> > delimiter. (You are welcome to implement it ;-).
> >
>
> I haven't ever used the shallow clone, but it looks still a bit different
> from what I thought originally, say, if I download linux-2.6.24.tar.bz2
> from kernel.org, that's about 40MB and should be a fair amount.
> I then unpack and "git init", I expect it to recognize it's a v2.6.24,
> and I can thereafter use "git fetch" to fetch those commits after
> v2.6.24 from git.kernel.org. Is this possible?
I tried shallow clone (depth 1) with a fairly old linux-2.6 repo and
the pack was 68MB. A bit bigger than 40MB but still acceptable IMO.
The tarball+git-init way, I don't think it work. Maybe kernel.org
could release shallow git bundles in addition to tarballs so users
like you can download a bundle, make a repo from it and keep up with
"git fetch".
--
Duy
next prev parent reply other threads:[~2008-03-01 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 9:23 Will git have a baseline feature or something alike? eric miao
2008-02-29 9:56 ` Sean
2008-02-29 10:38 ` Karl Hasselström
2008-02-29 13:21 ` Jakub Narebski
2008-03-01 7:04 ` Sam Vilain
2008-03-01 12:39 ` Jakub Narebski
2008-03-01 13:20 ` Sam Vilain
2008-03-02 19:38 ` Jan Hudec
2008-03-02 21:29 ` Martin Langhoff
2008-03-01 14:10 ` eric miao
2008-03-01 14:29 ` Nguyen Thai Ngoc Duy [this message]
2008-03-01 15:41 ` Jakub Narebski
2008-03-01 17:30 ` Eyvind Bernhardsen
2008-03-01 18:00 ` Jakub Narebski
2008-03-02 14:04 ` Shawn O. Pearce
2008-03-01 20:43 ` David Brown
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=fcaeb9bf0803010629v4894ad92ief4d5ef4257723e@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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 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).