From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Splitting off old history to ancillary repo
Date: Thu, 28 Aug 2008 14:40:23 +1200 [thread overview]
Message-ID: <46a038f90808271940w3aaf5c4ek6329e8066724c778@mail.gmail.com> (raw)
A project I've inherited has a codebase ~500KB in size. However, in
early history some large binary blobs were committed to the repo.
We've gotten rid of those, and they are not interesting to current
development. But an initial checkout still has to retrieve 60MiB, when
I'm sure the recent (and interesting) history fits in less than 1MB.
What is the state of grafts from a "keeping the repo mostly
transparently usable for newcomers" POV? Is there a new mechanims I
should look at?
Do we have a documented "here's how you split your repo with minimal
downsides to end users"? If you give me enough hints I could write it
:-)
The repo in question is http://dev.laptop.org/git?p=projects/xs-config;a=summary
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next reply other threads:[~2008-08-28 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 2:40 Martin Langhoff [this message]
2008-08-28 16:57 ` Splitting off old history to ancillary repo Michael J Gruber
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=46a038f90808271940w3aaf5c4ek6329e8066724c778@mail.gmail.com \
--to=martin.langhoff@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).