Moving an Incomplete Code Between Mercury Cash Desks

I checked the code on my desktop computer and worked on it. Now I'm leaving and I want these changes on my laptop.

One solution is to simply transfer the incomplete code and then pull them on my laptop. But that would mean that I have unrelated code in the repositories, which I would like to avoid.

What is the best way to handle this? Create and apply a patch? Use hg to move incomplete change?

+3
source share
4 answers

Here are three ways to do this. I will discuss all the pros and cons of each:

1: hg diff, diff, , hg import --nocommit

  • : , .
  • : mercurial ike DVCS. , .

2. , ( hg bundle -), , update , hg rollback , ( .

  • : push pull , mercurial intends
  • : . , 1 . , .

3. . -, , . repo , ,

  • . , DVCS. .
  • :

FWIW, 3. - , DVCS. , , , , / , , , .

, . ( ), : Mercurial?

+4

.... , "" ( Hg, , SVN Hg):

, , , , , , , , , ( , ) , !

"" - , DVCS "", , , , ) -:

( - SVN ), , "WIP" , , , ( ) WIP . , ( ), "", , , PUSH - - ... ( "" , ..). , , .

+1

Another interesting option (but a bit more involved) is to put the incomplete changes in MQ (first enable the mq extension) and the mq version (qinit -c). Then use qcommit to capture the current status of the fix queue and synchronize your work in progress by pulling and pressing mq.

0
source

This can be seen as uncultured, but I often use rsync to move "incomplete" repositories around SSH until I get to the point where there is something worthwhile.

0
source

Source: https://habr.com/ru/post/1722908/


All Articles