mercurial - How to pull latest remote changes into remote repo (while using mqueues) -


the hg book recommends following workflow updating mqueue patches when remote repository has been updated link:

hg qpush --all  # qsave depricated (according hg qsave --help).  appears have been # depricated since @ least 2010.  additionally, qsave not working in environment  # due organization's commit hooks hg qsave  hg pull  hg update --clean  hg qpush -m -a   

the qsave command says:

> command deprecated, use "hg rebase" instead. 

what new recommended workflow? want do:

  1. check out code
  2. make commits (probably not using mqueues)
  3. pull latest changes remote repo
  4. integrate changes repo. open rebase or merge workflow, want use kind of 3-way merge tool resolve conflicts

edit: workflow using is:

hg qpop --all hg pullup hg qpush # repeat until no patches left. 

the issue workflow generates .reject files.

i know can a:

hg qpush --all hg pull --rebase 

the issue don't know how abort or undo since modifies patches. think creates kind of backup described message: saved backup bundle /somedirectory/.hg/strip-backup/424323abc42a-backup.hg.


edit:

i did hg pull --rebase , worked well... think going use going forward. main uncomfort prefer merge rebase. want able see real parent of commits , how resolved conflicts. unfortunately, don't think merging , using mqueues compatible workflow. doesn't make sense pop patch has history on top of it...


edit:

thinking bit more, think workflow going try next time when know going have hairy conflicts:

# convert patches real commits:  hg qfinish # args  # pull remote changes  # merge remote changes 

i think in theory after doing rebase merges away in senario 7.


Comments

Popular posts from this blog

c++ - No viable overloaded operator for references a map -

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

java - Cannot secure connection using TLS -