From: Thomas Koch <thomas@koch.ro>
To: git@vger.kernel.org
Subject: [Request] Git export with hardlinks
Date: Wed, 6 Feb 2013 16:19:07 +0100 [thread overview]
Message-ID: <201302061619.07765.thomas@koch.ro> (raw)
Hi,
I'd like to script a git export command that can be given a list of already
exported worktrees and the tree SHA1s these worktrees correspond too. The git
export command should then for every file it wants to export lookup in the
existing worktrees whether an identical file is already present and in that
case hardlink to the new export location instead of writing the same file
again.
Use Case: A git based web deployment system that exports git trees to be
served by a web server. Every new deployment is written to a new folder. After
the export the web server should start serving new requests from the new
folder.
It might be possible that this is premature optimization. But I'd like to
learn more Python and dulwich by hacking this.
Do you have any additional thoughts or use cases about this?
Regards,
Thomas Koch, http://www.koch.ro
next reply other threads:[~2013-02-06 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 15:19 Thomas Koch [this message]
2013-02-08 9:58 ` [Request] Git export with hardlinks Jeff King
2013-02-10 10:33 ` Thomas Koch
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=201302061619.07765.thomas@koch.ro \
--to=thomas@koch.ro \
--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).