Mercurial: Did not pull before committing local changes and push. Created 8+ heads -
i read questions suggested while posing, ended getting confused :s made few changes , committed , pushed them. later came know repository pushed to, before pushed it. questions are:
q1. did pushing overwrite repository, i.e repository no longer have changes pushed before me?
q2. should in such cases? need have changes made, , other changes too, w/o having make other guy pull code, re-commit, re-push, , pulling again, same working copy.
q3. there anyway code can updated/pulled implicitly before commit/push?
q4. rebase option? read on documentation, changes perform on code not private.
assumptions:
- there aren't branches created. (well, created, different modules, , not concerned them).
- i use eclipse , mercurialeclipse.
edit: sorry if question (possible) duplicate of existing question.
when manage create medusa-repo in hg, determine branch going "mainline". go each sub-branch , perform process:
hg -r subbranch hg merge -r mainline-branch hg commit -m "merged main" hg -r mainline-branch hg merge -r subranch hg commit -m "brought in subchanges subbranch"
by merging subbranch first, make sure mainline doesn't damaged, can trivially merge mainline.
this not major crisis; requires working other developers start hitting same branch again in next day or so.
Comments
Post a Comment