|Re: [mdt-ocl.dev] Oops|
HiYou're misunderstanding 'ORIGIN-HEAD' which is where you last were when you last changed branches. It's a commit that hasn't been pushed upstream.
You should see a master branch that behaves consistently (except that since it is not 'current' you can delete it).
You should also see a 'wrongMaster' branch that is just clutter. Regards Ed On 11/07/2013 13:45, Adolfo Sanchez-Barbudo Herrera wrote:
On 11/07/2013 13:23, Ed Willink wrote:Just need to solve the inelegance that build.eclipse.org considers 'wrongMaster' to be the current branch.That sounds the problem I had one time. At that moment didn't know either, some git-based commands could make the the HEAD of the remote repository (ORIG-HEAD) be in place.I've just fetched from upstream, and indeed, I see the the ORIGIN-HEAD in an old commit:commit 1a5d322b407895667d010cc5ac187b321f15fe37 _______________________________________________ mdt-ocl.dev mailing list mdt-ocl.dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3349 / Virus Database: 3204/6481 - Release Date: 07/10/13
Back to the top