That looked so promising. We've both done changes in the TD chapter which it thinks are conflicts (but probably aren't really, I just plopped in a whole new section). (and for the record rather than sort it out, I just did a new clone of the whole repository. ;-) ) Ok, I think I'll just do my changes again. Just to double check before I do... it is still best to do them off of the lb42-pureodd-2 branch... right? -James On 15/12/15 14:22, Hugh Cayless wrote:
There’s a few things you could try. Depends a bit on what you’ve done and how your changes interact with Lou’s.
I think what I’d try first is:
git fetch git checkout lb42-pureodd-2 git checkout your_branch git rebase lb42-pureodd-2
That should re-run the commits you’ve made in your branch on top of the new pureodd branch and hopefully give you a branch that acts like you started from there in the first place.
I'd make a copy of your repo first though, just in case things don’t turn out the way you hope.
On Dec 15, 2015, at 9:07 , James Cummings
wrote: Hiya,
Is there a way to copy the changes I've made on one branch to another? Or move one branch (off another branch) to be tracking a different branch instead? (e.g. I made the 'processing-model' branch off of Lou's original lb42-pureodd branch and I want to move it to his current one.)
Suggestions? Or do I have to go do all the changes again?
-James -- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford