From: Ramsay Jones <ramsay@ramsay1•demon.co.uk>
To: Junio C Hamano <gitster@pobox•com>
Cc: Theodore Tso <tytso@mit•edu>,
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: Thu, 02 Aug 2007 19:08:02 +0100 [thread overview]
Message-ID: <46B21D82.5020802@ramsay1.demon.co.uk> (raw)
In-Reply-To: <7vr6mn5znm.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Are you suggesting to make -l the default for local, in other
> words? I personally do not make local clone often enough that I
> am not disturbed having to type extra " -l" on the command line.
>
> But giving a way to force "copy not hardlink" while still
> avoiding "the same as the networked case by doing pack transfer"
> overhead may be a good thing to do.
>
> Perhaps if the destination is local,
>
> - if -s is given, just set up alternates, do nothing else;
> - by default, do "always copy never hardlink";
> - with -l, do "hardlink if possible";
>
> Hmmmm...
>
About six weeks ago, I finally got around to installing Linux (ubuntu 7.04)
on my laptop. Naturally, I cloned my sparse and git repositories over from
the Windows XP partition. Unfortunately, that left me with a sparse repo that
I could not modify; during the clone cpio copied the object directory, with
perhaps a little too much fidelity, which resulted in a .git/objects tree
with 555 permissions (both files and directories). [It also set the file
timestamps with utime(), BTW]. A quick chmod fixed it up without problem,
but still ...
When I cloned the git repo, however, I forgot the -l parameter and git-clone
effectively did a "git-fetch-pack --all -k $repo", leaving me with a
working, and fully repacked, repository. Nice.
So, I was about to suggest that when invoked with -l, if the object database
cannot be linked, due to EXDEV for example, it should fall back to the
"fetch-pack" behaviour. Since I don't have access to a large repo, I can't
compare the filesystem-copy time versus the fetch-pack time for a "realistic"
repo, but I suppose the copy would always be faster. Oh Well.
Just a data point.
ATB,
Ramsay Jones
next prev parent reply other threads:[~2007-08-02 18:09 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
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 [this message]
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=46B21D82.5020802@ramsay1.demon.co.uk \
--to=ramsay@ramsay1$(echo .)demon.co.uk \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jnareb@gmail$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=tytso@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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