From: Theodore Tso <tytso@mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jakub Narebski <jnareb@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Git benchmark - comparison with Bazaar, Darcs, Git and Mercurial
Date: Wed, 1 Aug 2007 05:24:29 -0400 [thread overview]
Message-ID: <20070801092428.GB28106@thunk.org> (raw)
In-Reply-To: <7vodhrby6f.fsf@assigned-by-dhcp.cox.net>
On Tue, Jul 31, 2007 at 10:50:48PM -0700, Junio C Hamano wrote:
> I would call aversion to -l a superstition, while aversion to -s
> has a sound technical reasons. The latter means you need to know
> what you are doing --- namely, you are making the clone still
> dependent on the original.
So would you accept a patch which adds a git-config variable which
specifies whether or not local clones should use hard links by default
(defaulting to yes), and which adds a --no-hard-links option to
git-clone to override the config option?
I could imagine a situation where if you are using a git repository
exclusively on a local system, with no remote repositories to act as
backups, where you might want git clone to to make full copies to
provide backups in case of filesystem or disk induced corruption. But
most of the time there are enough copies of the the repo on other
machines that the need for making separate copies of the git
objects/packs isn't really needed.
- Ted
next prev parent reply other threads:[~2007-08-01 9:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 0:16 Git benchmark - comparison with Bazaar, Darcs, Git and Mercurial Jakub Narebski
2007-08-01 2:14 ` Linus Torvalds
2007-08-01 5:50 ` Junio C Hamano
2007-08-01 8:48 ` David Kastrup
2007-08-01 9:24 ` Theodore Tso [this message]
2007-08-01 10:15 ` Junio C Hamano
2007-08-01 13:20 ` Alex Riesen
2007-08-01 13:20 ` Alex Riesen
2007-08-01 13:23 ` Alex Riesen
2007-08-01 15:49 ` Carl Worth
2007-08-01 17:03 ` Linus Torvalds
2007-08-01 18:17 ` David Kastrup
2007-08-01 20:36 ` Florian Weimer
2007-08-02 6:09 ` Junio C Hamano
2007-08-02 10:29 ` David Kastrup
2007-08-03 0:51 ` Junio C Hamano
2007-08-03 6:14 ` David Kastrup
2007-08-03 8:20 ` Johan Herland
2007-08-01 22:03 ` Theodore Tso
2007-08-01 22:49 ` Brandon Casey
2007-08-02 4:02 ` Allan Wind
2007-08-02 4:13 ` Linus Torvalds
2007-08-01 22:18 ` Jakub Narebski
2007-08-02 11:19 ` Jakub Narebski
2007-08-02 18:08 ` Ramsay Jones
2007-08-01 8:33 ` Jakub Narebski
2007-08-01 8:48 ` Junio C Hamano
2007-08-01 23:51 ` Jakub Narebski
2007-08-01 2:17 ` 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=20070801092428.GB28106@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=torvalds@linux-foundation.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).