From: Thomas Koch <thomas@koch.ro>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [Request] Git export with hardlinks
Date: Sun, 10 Feb 2013 11:33:26 +0100 [thread overview]
Message-ID: <201302101133.28746.thomas@koch.ro> (raw)
In-Reply-To: <20130208095819.GA17220@sigill.intra.peff.net>
Jeff King:
> [...]
> So a full checkout is 24M. For the next deploy, we'll start by asking
> "cp" to duplicate the old, using hard links:
Hi Jeff,
thank you very much for your idea! It's good and simple. It just breaks down
for the case when a large folder got renamed.
But I already hacked the basic layout of the algorithm and it's not
complicated at all, I believe:
https://github.com/thkoch2001/git_export_hardlinks/blob/master/git_export_hardlinks.py
I had to interrupt work on this and could not yet finish and test it. But I
thought you might be interested. Maybe something like this might one day be
rewritten in C and become part of git core?
Regards,
Thomas Koch, http://www.koch.ro
next prev parent reply other threads:[~2013-02-10 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 15:19 [Request] Git export with hardlinks Thomas Koch
2013-02-08 9:58 ` Jeff King
2013-02-10 10:33 ` Thomas Koch [this message]
2013-02-11 17:13 ` Jeff King
2013-02-13 13:17 ` [ANN] First beta: " Thomas Koch
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=201302101133.28746.thomas@koch.ro \
--to=thomas@koch.ro \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.