Changes between Version 12 and Version 13 of WorkingGuideLines


Ignore:
Timestamp:
11/02/09 09:42:33 (15 years ago)
Author:
slavazanko
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingGuideLines

    v12 v13  
    102102 $ git pull                         // and check updates 
    103103}}} 
    104   Merge process, if you has just one commit: 
     104  Merge process: 
    105105{{{ 
    106  $ git merge --log 123_branch_name  // слияние с "master" той ветви, которую необходимо слить 
     106 $ git merge --log --no-ff 123_branch_name  // merge "123_branch_name" to "master" 
    107107}}} 
    108  
    109  If you have more than one commit: 
    110 {{{ 
    111  $ git merge --log --no-ff 123_branch_name  // слияние с "master" той ветви, которую необходимо слить 
    112 }}} 
    113    option --log add to commit list of merged patches, option --no-ff allow create merge commit in case where branch isn't child branch for current head, it should simplify understanding commit relation.  
     108   option --log add to commit list of merged patches, option --no-ff allow create merge commit in case where branch isn't child branch for current head, it should simplify understanding commit relation (use --no-ff option even you have one commit in branch).  
    114109 
    115110 Now you ready to update master branch on server:  
     
    122117 If you has any problems in merge process you should fix it manually and continue merge process, but try to check merge process before start to push or you can break branch. 
    123118 
    124  * Now you can close the ticket and the ticket will change into the testing state, and add to keywords name of branch you merge with (e.g. mater/commited-master). In ticket you must describe how get summary patch. For example: 
     119 * Now you can close the ticket and the ticket will change into the testing state, and rewrite 'Votes for changeset' to 'commited-master' text. Also, change value of 'Severity' fileld to 'merged'. In ticket comment you must describe how get summary patch. For example: 
    125120{{{ 
    126121fixed: 111111111111111^...222222222222222 # for multipatch 
     
    128123}}} 
    129124 where 111111111111111 - first commit; 222222222222222 - last commit 
     125Or you may describe just merge commit like: 
     126{{{ 
     127Merge changeset:111111111111111 
     128}}} 
     129 
    130130 * After some time of testing a ticketadmin will close it finally. 
    131131