From: "Jérémie NIKAES" <jeremie.nikaes@gmail.com>
To: git@vger.kernel.org
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Sylvain Boulme <Sylvain.Boulme@imag.fr>
Subject: Git fast-import : Warning duplicated ref: refs/remotes/origin/master
Date: Sun, 29 May 2011 18:09:31 +0200 [thread overview]
Message-ID: <BANLkTinTuEppMGO16z2sMkjV8FveCbrwEQ@mail.gmail.com> (raw)
Hi,
I am currently working on the git-mediawiki gateway project.
This project uses fast-import to get data from mediawiki. For each
revision from mediawiki, we generate a chunk of fast-export stream
looking like this :
commit refs/remotes/origin/master
mark :<int>
commiter <user> <address> <timestamp> +0000
data <sizeofcomment>
<comment>
M 644 inline <title>.wiki
data <sizeoffile>
<content>
At the end of a git clone mediawiki::http://ourwikitest, everything
looks perfectly fine, including the git log, but a "Warning duplicated
ref: refs/remotes/origin/master" is thrown. And indeed, it is
duplicated in .git/packedrefs
A git gc solves everything, but I wondered if there was a way to fix
this or if this was a known bug.
Thank you,
Regards,
--
Jérémie Nikaes
next reply other threads:[~2011-05-29 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 16:09 Jérémie NIKAES [this message]
2011-05-29 23:24 ` Git fast-import : Warning duplicated ref: refs/remotes/origin/master 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 ` [PATCH] Documentation: do not misinterpret refspecs as bold text (Re: Git fast-import : Warning duplicated ref: refs/remotes/origin/master) Jonathan Nieder
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=BANLkTinTuEppMGO16z2sMkjV8FveCbrwEQ@mail.gmail.com \
--to=jeremie.nikaes@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=Sylvain.Boulme@imag.fr \
--cc=git@vger.kernel.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).