From: Junio C Hamano <junkio@cox.net>
To: Pavel Roskin <proski@gnu.org>
Cc: GIT list <git@vger.kernel.org>
Subject: Re: RFC: script to add another remote
Date: Fri, 23 Feb 2007 00:43:26 -0800 [thread overview]
Message-ID: <7vr6sh8dsh.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1172219072.20390.17.camel@dv> (Pavel Roskin's message of "Fri, 23 Feb 2007 03:24:32 -0500")
Pavel Roskin <proski@gnu.org> writes:
>> So probably the next step would be to refactor some logic and
>> functionality out of git-clone, move them to git-remote, and
>> reimplement git-clone in terms of git-remote. Implementation of
>> "--more" option would become much simpler (or, almost free)
>> after that is done.
>
> Oh, I see. Thanks for the explanation.
Sorry for being incomplete --- obviously you cannot reimplement
clone with init and remote alone. You need 'fetch' ;-).
prev parent reply other threads:[~2007-02-23 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 22:16 RFC: script to add another remote Pavel Roskin
2007-02-22 22:24 ` Junio C Hamano
2007-02-23 8:14 ` Pavel Roskin
2007-02-23 8:21 ` Junio C Hamano
2007-02-23 8:24 ` Pavel Roskin
2007-02-23 8:43 ` Junio C Hamano [this message]
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=7vr6sh8dsh.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=proski@gnu.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.
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).