Changes between Version 9 and Version 10 of Moving to Git


Ignore:
Timestamp:
Jun 22, 2009, 3:41:09 PM (16 years ago)
Author:
joe.mason@torchmobile.com
Comment:

Add link to evmar's doc

Legend:

Unmodified
Added
Removed
Modified

  • Moving to Git

    v9 v10  
    2626
    2727    Another option is to copy your existing branch (which is very cheap) and then make the changes to the new branch, again with git-rebase, then publish the new branch.  For this we would probably want to define a standard naming scheme for patch review branches, such as including an iteration number or the date in the branch name, to avoid a confusing mess of names.
     28
     29    evmar's doc describing [http://neugierig.org/software/git/?url=git-cl/tree/README.codereview Chrome's git/reitveld workflow] discusses some of these issues in more depth
    2830
    2931 * Would allow us to do away with manually editing/resolving ChangeLog files: