git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junkio@cox.net>
Cc: GIT list <git@vger.kernel.org>
Subject: Re: RFC: script to add another remote
Date: Fri, 23 Feb 2007 03:14:28 -0500	[thread overview]
Message-ID: <1172218468.20390.15.camel@dv> (raw)
In-Reply-To: <7v8xepde5g.fsf@assigned-by-dhcp.cox.net>

On Thu, 2007-02-22 at 14:24 -0800, Junio C Hamano wrote:
> Pavel Roskin <proski@gnu.org> writes:
> 
> > It's interesting that git-clone-more can be used instead of git-clone.
> > I can use it e.g. to check out git in an empty directory:
> >
> > git-init
> > git-clone-more git://www.kernel.org/pub/scm/git/git.git git
> 
> Isn't that what "git remote" is about?

I don't understand your question.  "git remote" doesn't provide this
functionality by itself.  "git remote" is used by git-clone-more.  I
wish I were missing the obvious, but just mentioning "git remote" to me
doesn't seem to help.

I see that the manual for "git-remote" includes an example repeating
some parts of git-clone-more.  That's another evidence that the
functionality provided by git-clone-more is needed.

It looks like git-clone should be extended to support cloning of a
repository on top of the existing one.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2007-02-23  8:14 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 [this message]
2007-02-23  8:21     ` Junio C Hamano
2007-02-23  8:24       ` Pavel Roskin
2007-02-23  8:43         ` Junio C Hamano

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=1172218468.20390.15.camel@dv \
    --to=proski@gnu.org \
    --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).