git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: More problems...

From
Petr Baudis <pasky@ucw.cz>
Date
May 3, 2005, 01:48 UTC
Message-ID
<20050503014816.GQ20818@pasky.ji.cz>
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
Previous: Linus TorvaldsNext: Daniel Barkalow
Message 16 of 24 in “More problems...”
  1. Russell KingApr 29, 2005
  2. Russell KingApr 29, 2005
  3. Linus TorvaldsApr 29, 2005
  4. Petr BaudisApr 29, 2005
  5. Ryan AndersonApr 29, 2005
  6. Thomas GlanzmannApr 29, 2005
  7. Linus TorvaldsApr 29, 2005
  8. Junio C HamanoApr 29, 2005
  9. Russell KingApr 29, 2005
  10. Anton AltaparmakovApr 29, 2005
  11. Petr BaudisMay 2, 2005
  12. Dave KleikampMay 2, 2005
  13. Thomas GlanzmannMay 2, 2005
  14. Anton AltaparmakovMay 2, 2005
  15. Linus TorvaldsMay 2, 2005
  16. Petr BaudisMay 3, 2005
  17. Daniel BarkalowMay 3, 2005
  18. Andreas GalMay 3, 2005
  19. Junio C HamanoMay 3, 2005
  20. Daniel BarkalowApr 29, 2005
  21. Junio C HamanoApr 29, 2005
  22. Split out "pull" from particular methodsDaniel Barkalow, Apr 30, 2005
  23. Add git-relink-script, a tool to hardlink two existing repositories.Ryan Anderson, May 4, 2005
  24. Petr BaudisMay 2, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.