From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Please undo "Use git-merge instead of git-resolve in
Date: Fri, 23 Sep 2005 11:57:42 +0200 [thread overview]
Message-ID: <20050923095742.GC10255@pasky.or.cz> (raw)
In-Reply-To: <7vslvwcelj.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Fri, Sep 23, 2005 at 11:34:16AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> 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?
Yes, exactly that. You get it by doing cg-clone -l /local/path. O(1)
cloning, but it has its downsides and dangers which I tried to describe
in the cg-clone documentation.
> > * 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)?
Just that if the reference pointer did not change, you don't try to pull
any objects. Speeds things up somewhat, and now it should always work
(well, cg-fetch has -f which makes it always try objects as well, in
case something went wrong anyway).
> > * 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.
Good.
> 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.
cg-clone just basically does cg-init && cg-fetch, and I'd really want to
keep it on that. So effectively, cg-clone over http just runs
git-http-fetch and trusts it to do the right thing (reasonably fast).
Recursive wget is used only for fetching tags (and it actually seems to
work nicely, when directory listing is enabled, obviously). Yes, I
should teach cg-fetch about info/refs too.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-09-23 9:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 18:32 Please undo "Use git-merge instead of git-resolve in Jon Loeliger
2005-09-22 19:10 ` Petr Baudis
[not found] ` <34462.10.10.10.28.1127417134.squirrel@linux1>
2005-09-22 19:25 ` Sean
2005-09-22 22:22 ` Junio C Hamano
[not found] ` <55917.10.10.10.28.1127429674.squirrel@linux1>
2005-09-22 22:54 ` Sean
2005-09-23 9:10 ` Petr Baudis
2005-09-23 9:34 ` Junio C Hamano
2005-09-23 9:57 ` Petr Baudis [this message]
2005-09-23 21:07 ` Daniel Barkalow
2005-09-24 6:19 ` Junio C Hamano
2005-09-22 21:12 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2005-09-23 13:51 Jon Loeliger
2005-09-22 19:12 Jon Loeliger
2005-09-22 21:22 ` Linus Torvalds
2005-09-22 21:37 ` Linus Torvalds
2005-09-22 21:57 ` Daniel Barkalow
2005-09-22 22:05 ` Linus Torvalds
2005-09-22 14:55 Jon Loeliger
2005-09-22 16:01 ` Petr Baudis
2005-09-22 16:06 ` Linus Torvalds
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=20050923095742.GC10255@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).