From: "Jérémie NIKAES" <jeremie.nikaes@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
git@vger.kernel.org, Sylvain Boulme <Sylvain.Boulme@imag.fr>,
Mike Hommey <mh@glandium.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: Git fast-import : Warning duplicated ref: refs/remotes/origin/master
Date: Mon, 30 May 2011 22:32:21 +0200 [thread overview]
Message-ID: <BANLkTi=+v0Jt2+xgxy=qV+BT7pOUMpoMtw@mail.gmail.com> (raw)
In-Reply-To: <20110530201351.GB14427@elie>
> Matthieu Moy wrote:
>> Jonathan Nieder <jrnieder@gmail.com> writes:
>> If so, I don't understand why the distinction between 1) and 2) is
>> necessary, and why not to fetch directly into refs/remotes/origin/. IOW,
>> in which case is refs/remotes/origin/master different from
>> refs/mediawiki/origin/master for example?
>
> That's a good question. One answer is that fetching to elsewhere
> allows the transport machinery to take care of rejecting non-fast-forward
> fetches and pretty-printing the ref update information:
>
> From mediawiki::http://localhost/mediawiki
> 479ee21..accd2c1 master -> origin/master
>
> I think in the long term, importing to no ref at all as Sverre
> suggested and teaching the transport-helper to do the ref update would
> make more sense.
Well yes that would indeed make more sense. It feels weird to have to
do it like this.
Anyways, thanks a lot again for your help, a rfc patch should come
relatively quickly with the project in its current state.
Regards,
--
Jérémie Nikaes
next prev parent reply other threads:[~2011-05-30 20:32 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 ` [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 [this message]
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='BANLkTi=+v0Jt2+xgxy=qV+BT7pOUMpoMtw@mail.gmail.com' \
--to=jeremie.nikaes@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=Sylvain.Boulme@imag.fr \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mh@glandium.org \
--cc=srabbelier@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.