[GRASS-dev] backporting help for SVN

William Kyngesburye woklist at kyngchaos.com
Tue Mar 25 20:53:30 EDT 2008


Are there any policies on developers backporting their changes to  
release branches?  Do it theirselves?  Ask another to do it (ie you)  
to keep some review sanity?

I don't want to mess it up in attempting to do it myself.  I was  
hoping it would be as simple as "apply this trunk changeset to that  
branch", but it looks like I now need to have a local copy of the  
branch so I can commit the merges.  Though, mine are simple enough  
(mostly), and isolated, that I could just do a diff and commit.

On Mar 24, 2008, at 1:19 AM, Glynn Clements wrote:

> William Kyngesburye wrote:
>> Back in November there was discussion on how to backport in CVS.  How
>> about SVN?  I have one old change that hasn't made it to the RCs yet.
> http://svnbook.red-bean.com/en/1.4/svn.branchmerge.copychanges.html
> -- 
> Glynn Clements <glynn at gclements.plus.com>

William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>

"Oh, look, I seem to have fallen down a deep, dark hole.  Now what  
does that remind me of?  Ah, yes - life."

- Marvin

More information about the grass-dev mailing list