Home > Back-end >  SVN commit, about migration to B after the warehouse, and submit to return to A warehouse
SVN commit, about migration to B after the warehouse, and submit to return to A warehouse

Time:10-17

SVN commit, cause it is
Initial code submitted to A warehouse, then data migration to B warehouse, and then after B warehouse submitted several versions, and to commit to A warehouse, but this time tip



Could you tell me how to handle this time

CodePudding user response:

Only the client won't solve

Since A checkout, manually modify the code to submit again

CodePudding user response:

reference 1st floor tianfang response:
client only cannot solve the

Since A checkout, manually modify the code to submit


Good, is a manual revert to the corresponding version, and then modify the code file individually so commit is, ok

CodePudding user response:



refer to the second floor GroovRain response:
Quote: refer to 1st floor tianfang response:

Only the client won't solve

Since A checkout, manually modify the code to submit


Good, is a manual revert to the corresponding version, and then modify the code file individually so commit, good


Yes

Multiple SVN is asking for trouble

CodePudding user response:

reference tianfang reply: 3/f
Quote: refer to the second floor GroovRain response:

Quote: refer to 1st floor tianfang response:

Only the client won't solve

Since A checkout, manually modify the code to submit


Good, is a manual revert to the corresponding version, and then modify the code file individually so commit, good


Yes

Multiple SVN is asking for trouble


Ha ha because initially thought A warehouse is out of order, mobile B temporary warehouse, A good warehouse suddenly now,,,
But I tried to revert, then replace the corresponding update files, or suggest expectation and reality,,,,
  • Related