From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Florian Achleitner <florian.achleitner.2.6.31@gmail.com>
Cc: jrnieder@gmail.com, davidbarr@google.com, git@vger.kernel.org
Subject: Re: GSOC remote-svn
Date: Mon, 23 Jul 2012 09:59:40 +0200 [thread overview]
Message-ID: <vpqr4s2nc0j.fsf@bauges.imag.fr> (raw)
In-Reply-To: <4514544.Xip1OCQ7Uj@flomedio> (Florian Achleitner's message of "Sun, 22 Jul 2012 23:03:27 +0200")
Florian Achleitner <florian.achleitner.2.6.31@gmail.com> writes:
> But my remote-helper didn't advertise the refspec capability, so transport-
> helper assumed it imports to refs/heads/master, which is the default import
> refspec.
The man page for git-remote-helpers says:
refspec <refspec>
[...] It is recommended that all importers providing the import
capability use this.
I'm not sure I fully understand the rationale, but one difference
between refs/<remote name>/* and refs/remotes/<remote name> is that
refs/remotes/ is automatically updated by Git on push, while the private
namespace isn't (it only receives updates when importing).
I played a bit with that it git-remote-mediawiki. There's a
configuration variable mediawiki.dumbPush that controls what "push"
does. It can either export the local history without touching local
metadata (and then, it is expected that the user does a "git pull
--rebase" right after to re-import the history), or update the local
metadata (private ref, and notes that keep the <local commit> <->
<remote revision number> map), so that the next "git pull" says
"Already up to date.".
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-07-23 8:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 21:03 GSOC remote-svn Florian Achleitner
2012-07-22 21:43 ` Jonathan Nieder
2012-07-23 9:42 ` Florian Achleitner
2012-07-23 12:04 ` Jonathan Nieder
2012-07-23 12:44 ` [PATCH] Add a svnrdump-simulator replaying a dump file for testing Florian Achleitner
2012-07-23 12:59 ` Jonathan Nieder
2012-07-23 13:16 ` Florian Achleitner
2012-07-23 13:16 ` Florian Achleitner
2012-07-23 16:24 ` Matthieu Moy
2012-07-23 19:28 ` Florian Achleitner
2012-07-23 19:46 ` Matthieu Moy
2012-07-23 20:02 ` Jeff King
2012-07-23 15:06 ` Junio C Hamano
2012-07-23 20:08 ` Florian Achleitner
2012-07-23 20:38 ` Junio C Hamano
2012-07-24 19:50 ` Jonathan Nieder
2012-07-25 6:20 ` Florian Achleitner
2012-07-24 12:06 ` Erik Faye-Lund
2012-07-23 7:59 ` Matthieu Moy [this message]
2012-07-23 11:59 ` GSOC remote-svn Jonathan Nieder
2012-07-23 9:42 ` Florian Achleitner
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=vpqr4s2nc0j.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=davidbarr@google.com \
--cc=florian.achleitner.2.6.31@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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.