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

Re: Please undo "Use git-merge instead of git-resolve in

From
Junio C Hamano <junkio@cox.net>
Date
Sep 23, 2005, 09:34 UTC
Message-ID
<7vslvwcelj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20050923091012.GA10255@pasky.or.cz>
Petr Baudis <pasky@suse.cz> writes:
> 	* cg-fetch can do with symlinked object database

Do you mean ".git/object" in the repository you are fetching into is a symlink to somewhere, or something else?

> 	* cg-fetch will hardlink if possible when fetching locally

True, git-fetch and git-clone try to use pack protocols by default, which is debatable. Adding -l (similar to what git-clone does) would not be too hard, if enough people want it.

> 	* cg-fetch won't do useless fetches when we are already
> 	  up-to-date

Care to explain? Perhaps you are talking about rsync transport (in which case I would not be surprised)?

> 	* I'm not sure if I could call git-fetch to do the initial
> 	  fetch during clone
    $ git-init-db && git fetch http://kernel.org/pub/scm/git/git.git
should work.

There is another minor "con", if you include git-clone in the discussion. Over http transport, it refuses to run against a remote repository that does not have info/refs and info/packs, even if it is not packed. I think cg-clone uses recursive wget for directory traversal and does not have to use them.

Previous: Petr BaudisNext: Petr Baudis
Message 8 of 11 in “Re: Please undo "Use git-merge instead of git-resolve in”
  1. Jon LoeligerSep 22, 2005
  2. Petr BaudisSep 22, 2005
  3. SeanSep 22, 2005
  4. Junio C HamanoSep 22, 2005
  5. SeanSep 22, 2005
  6. Linus TorvaldsSep 22, 2005
  7. Petr BaudisSep 23, 2005
  8. Junio C HamanoSep 23, 2005
  9. Petr BaudisSep 23, 2005
  10. Daniel BarkalowSep 23, 2005
  11. Junio C HamanoSep 24, 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.