Re: Git fast-import : Warning duplicated ref: refs/remotes/origin/master
- From
- Jérémie NIKAES <jeremie.nikaes@gmail.com>
- Date
- May 30, 2011, 20:32 UTC
- Message-ID
- <BANLkTi=+v0Jt2+xgxy=qV+BT7pOUMpoMtw@mail.gmail.com>
- In-Reply-To
- <20110530201351.GB14427@elie>
> Matthieu Moy wrote: >> Jonathan Nieder <jrnieder@gmail.com> writes:
Show 15 quoted lines
>> 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