Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
overview paper co-author invitation
#19
Now that I work more with mercurial I see that the work flow described above is not completely correct for pulling changes from the bitbucket repository.

To keep your local repository consistent with the remote bitbucket repository you have to do the following:

Code:
> hg pull
This pulls changes from the remote repository

> hg merge
This merges these changes into your current repository.

If there are conflicts, i.e. someone else changed the same part of the file that you changed too, you have to resolve conflicts. These are marked with <<<<< and >>>>>> in the file.
If you have done this, do a
> hg resolve -m
> hg commit
After that you can work as usual on your files, i.e. make some changes, make some commits, and if you reached some official state you can push it to the bitbucket repository. And everybody else can pull your changes.
Reply


Messages In This Thread
overview paper co-author invitation - by bo198214 - 06/02/2009, 01:06 AM
meeting ? - by tommy1729 - 06/06/2009, 10:42 PM
RE: overview paper co-author invitation - by bo198214 - 08/06/2009, 05:08 AM

Possibly Related Threads...
Thread Author Replies Views Last Post
  Old Research Paper andydude 3 2,714 01/24/2018, 04:12 AM
Last Post: andydude
  changing terminology (was: overview paper co-author invitation) andydude 49 57,783 11/05/2009, 02:06 AM
Last Post: Base-Acid Tetration
  Paper with iteration intro andydude 4 6,061 05/13/2009, 07:53 AM
Last Post: andydude



Users browsing this thread: 1 Guest(s)