From: Thomas Glanzmann <thomas@glanzmann.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: GIT <git@vger.kernel.org>
Subject: Re: RFD Use git for off-site backups
Date: Sun, 13 May 2007 13:18:41 +0200 [thread overview]
Message-ID: <20070513111841.GA24392@cip.informatik.uni-erlangen.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0705131251370.6410@racer.site>
Hello,
> I think that this setup (have objects remotely) will kill performance
> pretty quickly. You have to compare to other blobs in order to find
> reasonable deltas...
so true. I thought about that myself just after I sent the eMail.
> There has been talk about pre-commit scripts which put this
> information into a file, and a post-checkout script to resurrect these
> metadata, but I haven't seen functional versions of these scripts yet.
I thought there is a way to add information without loosing compability
with current git versions. But maybe I am just mistaken.
Thomas
next prev parent reply other threads:[~2007-05-13 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 9:34 RFD Use git for off-site backups Thomas Glanzmann
2007-05-13 11:16 ` Johannes Schindelin
2007-05-13 11:18 ` Thomas Glanzmann [this message]
2007-05-13 12:34 ` Jan Hudec
2007-05-13 23:42 ` Shawn O. Pearce
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=20070513111841.GA24392@cip.informatik.uni-erlangen.de \
--to=thomas@glanzmann.de \
--cc=Johannes.Schindelin@gmx.de \
--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).