Changes between Version 15 and Version 16 of HowToBackport


Ignore:
Timestamp:
04/14/13 03:55:19 (12 years ago)
Author:
hamish
Comment:

example

Legend:

Unmodified
Added
Removed
Modified
  • HowToBackport

    v15 v16  
    2929
    3030To use them, first make sure all branches are up to date (`svn up`) and clean (`svn diff`),
    31 then `cd` into the top of the source tree you want to ''pull '''in''' to''. If you try to run it from the module's own subdir it will fail.
     31then `cd` into the '''top''' of the source tree you want to ''pull '''in''' to''. If you try to run it from the module's own subdir it will fail.
    3232Then run the script named for the branch you want to pull ''from'', followed by the revision number of the change you wish to merge (no leading "r" or [square brackets] around the rev number please). Mind that you might want to run '`svn propdel svn:mergeinfo .`' before doing an untargeted 'svn commit'.
    3333
     34Example:
     35{{{
     36 # make the original edit
     37 cd devbr6
     38 svn diff lib/gis/parser.c
     39 svn up lib/gis/parser.c
     40 vi lib/gis/parser.c
     41 svn diff lib/gis/parser.c
     42 # .. run make; test the change ..
     43 svn commit lib/gis/parser.c   # note the rev number of the commit
     44
     45 # now backport it
     46 cd ../relbr64
     47 svn diff lib/gis/parser.c
     48 svn up lib/gis/parser.c
     49 svn65merge 54321
     50 svn diff lib/gis/parser.c
     51 # .. run make; test the change ..
     52 svn commit lib/gis/parser.c
     53}}}
    3454== Comparing branches ==
    3555