From: Paolo Bonzini <bonzini@gnu.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [RFC] Moving "git remote add --mirror blah" functionality to "git clone --bare --origin=blah"
Date: Wed, 23 Apr 2008 22:06:00 +0200 [thread overview]
Message-ID: <480F96A8.6020304@gnu.org> (raw)
In-Reply-To: <7vhcdstv0f.fsf@gitster.siamese.dyndns.org>
> *1* In that sense, a more sensible order than rewriting "clone" in C in
> its current form would be to make necessary enhancements to the components
> in this sequence that need to implement clone, figure out how they should
> fit together and first make "clone" a four-liner shell script. Then
> rewriting the result in C may become more trivial.
On the other hand, a C version may have the necessary APIs available to
support this kind of enhancement, but the APIs may not be there for a
shell script.
It seems useless to have an option in "git remote add" just because it
might be necessary in a future refactoring of "git clone", but without a
good use case beside that one -- because right now "git remote add
--mirror" is close to useless: anyone who needs it 99% of the time knows
how to hack the config, unlike people who just want a quick way to
remotely backup of their repository.
Paolo
next prev parent reply other threads:[~2008-04-23 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 8:28 [RFC] Moving "git remote add --mirror blah" functionality to "git clone --bare --origin=blah" Paolo Bonzini
2008-04-23 9:59 ` Johannes Schindelin
2008-04-23 16:07 ` Junio C Hamano
2008-04-23 16:56 ` Daniel Barkalow
2008-04-23 22:25 ` Jeff King
2008-04-23 20:06 ` Paolo Bonzini [this message]
2008-04-23 22:02 ` Junio C Hamano
2008-04-23 22:42 ` Johannes Schindelin
2008-04-24 6:23 ` Paolo Bonzini
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=480F96A8.6020304@gnu.org \
--to=bonzini@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.