From: "eric miao" <eric.y.miao@gmail.com>
To: git@vger.kernel.org
Subject: Will git have a baseline feature or something alike?
Date: Fri, 29 Feb 2008 17:23:37 +0800 [thread overview]
Message-ID: <f17812d70802290123raa099bag17a6f7b89de65dd4@mail.gmail.com> (raw)
All,
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.
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.
E.g.
1. user downloads a released tarball
2. and build a repository
3. and "git fetch" will find the current repository is identical to
a baseline in the remote, and fetches only commits after
that baseline
4. continue the development work
The above steps with current git will generate a totally different
hash value for the files in the downloaded tarball, thus making
it failed to fetch commits thereafter.
I know the history is usually mixed with multiple branches, which
makes this baseline feature a bit difficult to implement. It should
be a nice feature, though.
--
Cheers
- eric
next reply other threads:[~2008-02-29 9:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 9:23 eric miao [this message]
2008-02-29 9:56 ` Will git have a baseline feature or something alike? 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
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=f17812d70802290123raa099bag17a6f7b89de65dd4@mail.gmail.com \
--to=eric.y.miao@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).