From: "Jérémie NIKAES" <jeremie.nikaes@gmail.com>
To: Jonathan Nieder <jrnieder@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>
Subject: Re: Git fast-import : Warning duplicated ref: refs/remotes/origin/master
Date: Mon, 30 May 2011 17:07:26 +0200 [thread overview]
Message-ID: <BANLkTinRscvPLHbob55pxhXSTKqm+eSF6g@mail.gmail.com> (raw)
In-Reply-To: <20110530145203.GA10879@elie>
>
> Could you push a branch exhibiting the problem? The reason I ask
> is that searching with
>
> git grep -F -e 'duplicated ref' origin/master
>
> in git.git yields no hits for me, so I wanted to reproduce this to get
> the exact error message or figure out which program is printing it.
>
> Thanks.
>
Ok I just committed my changes to the master branch, feel free to pull
and try it out.
Thanks for your help
--
Jérémie Nikaes
next prev parent reply other threads:[~2011-05-30 15:07 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 [this message]
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=BANLkTinRscvPLHbob55pxhXSTKqm+eSF6g@mail.gmail.com \
--to=jeremie.nikaes@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=Sylvain.Boulme@imag.fr \
--cc=git@vger.kernel.org \
--cc=jrnieder@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).