From: Jonathan Nieder <jrnieder@gmail.com>
To: "Jérémie NIKAES" <jeremie.nikaes@gmail.com>
Cc: git@vger.kernel.org, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Sylvain Boulme <Sylvain.Boulme@imag.fr>,
Mike Hommey <mh@glandium.org>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH] Documentation: do not misinterpret refspecs as bold text (Re: Git fast-import : Warning duplicated ref: refs/remotes/origin/master)
Date: Mon, 30 May 2011 10:52:56 -0500 [thread overview]
Message-ID: <20110530155256.GC10879@elie> (raw)
In-Reply-To: <BANLkTinRscvPLHbob55pxhXSTKqm+eSF6g@mail.gmail.com>
Jérémie NIKAES wrote:
> Ok I just committed my changes to the master branch, feel free to pull
> and try it out.
Nice. Now I get
| $ git fetch --all
[...]
| Fetching & writing export data...
| 1/2: Revision n°7 of New_page
| 2/2: Revision n°8 of New_page
|
| error: Ref refs/remotes/origin/master is at d94a46270250454f1fc6c1fb47abfde31a2196c9 but expected dfb79bbc658333d5c9b0427b71f6b1bc48629949
| From mediawiki::http://localhost/mediawiki
| ! dfb79bb...c57c15b master -> origin/master (unable to update local ref)
| error: Could not fetch origin
which means that the transport machinery thought the helper was going
to be fetching directly to "master". I suspect you will want a
'refspec' capability like
refspec refs/heads/*:refs/mediawiki/${remotename}/*
to fix this.
Cc-ing Daniel who invented v1.7.0-rc0~62^2~19 (Allow helper to map
private ref names into normal names, 2009-11-18). What namespace
should a helper use when asked to fetch to FETCH_HEAD without a remote
name, like
git fetch mediawiki::testwiki
?
-- >8 --
Subject: Documentation: do not misinterpret refspecs as bold text
In v1.7.3.3~2 (Documentation: do not misinterpret pull refspec as bold
text, 2010-12-03) many uses of asterisks in expressions like
"refs/heads/*:refs/svn/origin/branches/*" were escaped as {asterisk}
to avoid being treated as delimiters for bold text, but these two were
missed.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
Documentation/git-remote-helpers.txt | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-remote-helpers.txt b/Documentation/git-remote-helpers.txt
index 87cd11f..58f6ad4 100644
--- a/Documentation/git-remote-helpers.txt
+++ b/Documentation/git-remote-helpers.txt
@@ -181,11 +181,11 @@ CAPABILITIES
When using the import command, expect the source ref to have
been written to the destination ref. The earliest applicable
refspec takes precedence. For example
- "refs/heads/*:refs/svn/origin/branches/*" means that, after an
- "import refs/heads/name", the script has written to
+ "refs/heads/{asterisk}:refs/svn/origin/branches/{asterisk}" means
+ that, after an "import refs/heads/name", the script has written to
refs/svn/origin/branches/name. If this capability is used at
all, it must cover all refs reported by the list command; if
- it is not used, it is effectively "*:*"
+ it is not used, it is effectively "{asterisk}:{asterisk}"
REF LIST ATTRIBUTES
-------------------
--
1.7.5.3
next prev parent reply other threads:[~2011-05-30 15:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 16:09 Git fast-import : Warning duplicated ref: refs/remotes/origin/master Jérémie NIKAES
2011-05-29 23:24 ` Jonathan Nieder
2011-05-30 14:44 ` Jérémie NIKAES
2011-05-30 14:52 ` Jonathan Nieder
2011-05-30 15:07 ` Jérémie NIKAES
2011-05-30 15:52 ` Jonathan Nieder [this message]
2011-05-30 16:40 ` remote helpers: best practices for using the "refspec" capability Jonathan Nieder
2011-05-30 17:43 ` Daniel Barkalow
2011-05-30 18:04 ` Sverre Rabbelier
2011-05-30 17:35 ` Git fast-import : Warning duplicated ref: refs/remotes/origin/master Jonathan Nieder
2011-05-30 19:46 ` Matthieu Moy
2011-05-30 19:55 ` Jérémie NIKAES
2011-05-30 20:13 ` Jonathan Nieder
2011-05-30 20:32 ` Jérémie NIKAES
2011-05-30 23:09 ` Sverre Rabbelier
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=20110530155256.GC10879@elie \
--to=jrnieder@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=Sylvain.Boulme@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeremie.nikaes@gmail.com \
--cc=mh@glandium.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).