From: Petr Baudis <pasky@ucw.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
Russell King <rmk@arm.linux.org.uk>,
Junio C Hamano <junkio@cox.net>,
Ryan Anderson <ryan@michonline.com>,
git@vger.kernel.org
Subject: Re: More problems...
Date: Tue, 3 May 2005 03:48:16 +0200 [thread overview]
Message-ID: <20050503014816.GQ20818@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.58.0505021509530.3594@ppc970.osdl.org>
Dear diary, on Tue, May 03, 2005 at 12:19:16AM CEST, I got a letter
where Linus Torvalds <torvalds@osdl.org> told me that...
> But for "normal" situations, where you have a tree or two, the hardlinking
> win might not be big enough to warrant the maintenance headache. With
> hardlinking, you _do_ need to "trust" the other trees to some degree.
As long as the trees aren't yours and you aren't doing something really
horrible with them...
$ time git-local-pull -a -l $(cat ~/git-devel/.git/HEAD) ~/git-devel/.git/
real 0m0.332s
$ time git-local-pull -a $(cat ~/git-devel/.git/HEAD) ~/git-devel/.git/
real 0m4.306s
And this is only 13M Cogito objects database. I think one of the
important things is to encourage branching, therefore it must be fast
enough; that's why I really wanted to do hardlinks. The disk space is
important, but the speed hit probably equally (if not more) so.
BTW, the object database files should have 0444 or such; they really
_are_ read-only and making them so mode-wise could help against some
mistakes too.
It's clear that Cogito should have a way to choose whether to hardlink
or copy; the question is which one should be the default one and how
should it be specified. I thought about using file:// vs. just local
path to differentiate between copy and hardlinking, but that'd be
totally non-obvious, therefore bad UI-wise.
BTW, I've just committed support for pulling from remote repositories
over the HTTP and SSH protocols (http://your.git/repo,
git+ssh://root@git.nasa.gov/srv/git/mars) (note that I was unable to
test the SSH stuff properly now; success reports or patches welcome).
Also, the local hardlinking access is now done over git-local-pull,
therefore the cp errors should go away now.
I'm not yet decided whether locations like
kernel.org:/pub/scm/cogito/cogito.git
should invoke rsync, rpull, throw an error or print a fortune cookie.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-05-03 1:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 16:01 More problems Russell King
2005-04-29 16:12 ` Russell King
2005-04-29 17:51 ` Linus Torvalds
2005-04-29 18:27 ` Petr Baudis
2005-04-29 19:50 ` Ryan Anderson
2005-04-29 20:03 ` Thomas Glanzmann
2005-04-29 20:21 ` Linus Torvalds
2005-04-29 21:07 ` Junio C Hamano
2005-04-29 21:19 ` Russell King
2005-04-29 21:57 ` Anton Altaparmakov
2005-05-02 19:33 ` Petr Baudis
2005-05-02 19:44 ` Dave Kleikamp
2005-05-02 19:51 ` Thomas Glanzmann
2005-05-02 22:01 ` Anton Altaparmakov
2005-05-02 22:19 ` Linus Torvalds
2005-05-03 1:48 ` Petr Baudis [this message]
2005-05-03 2:56 ` Daniel Barkalow
2005-05-03 15:00 ` Andreas Gal
2005-05-03 19:18 ` Junio C Hamano
2005-04-29 21:27 ` Daniel Barkalow
2005-04-29 22:01 ` Junio C Hamano
2005-04-30 5:36 ` [PATCH] Split out "pull" from particular methods Daniel Barkalow
2005-05-04 5:54 ` [PATCH] Add git-relink-script, a tool to hardlink two existing repositories Ryan Anderson
2005-05-02 21:13 ` More problems Petr Baudis
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050503014816.GQ20818@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=aia21@cam.ac.uk \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=rmk@arm.linux.org.uk \
--cc=ryan@michonline.com \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).