From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Git Mailing List <git@vger.kernel.org>, Junio C Hamano <junkio@cox.net>
Subject: Re: [RFC] Moving "git remote add --mirror blah" functionality to "git clone --bare --origin=blah"
Date: Wed, 23 Apr 2008 10:59:59 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0804231057470.4181@eeepc-johanness> (raw)
In-Reply-To: <480EF334.1090907@gnu.org>
Hi,
On Wed, 23 Apr 2008, Paolo Bonzini wrote:
> In the thread "git remote update -> rejected" Junio and Johannes came to
> the conclusion that "--mirror means that you do not have local
> branches", because "you give control away to the other end on the ref
> namespace". Furthermore, it was agreed that --mirror currently makes
> sense mostly (or only?) on a bare repository.
Yes. But the opposite may not be true: if you plan to work on many
workdirs, but the same repository, you might still want to have separate
remotes layout.
In any case, I think that this discussion is too early: clone should be
builtin first, making things much simpler because of being a very thin
layer on top of init && remote && fetch.
But yes, there is a lot of work left on the builtin-clone to make it so.
Ciao,
Dscho
next prev parent reply other threads:[~2008-04-23 10:01 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 [this message]
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
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=alpine.DEB.1.00.0804231057470.4181@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=bonzini@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