Re: Best practice for customization to allow persistance between versions?

[woodvorg <..hidden..>]

Ed Wildgoose-2 wrote:
> Check it all out using git, branch it and make your edits to your hearts 
> content...
> 
> ...all the cool cats are using git these days... ;-)

Now that's a much better idea! So when a new version comes out, I check it
out and just merge the new release branch with my branch? Are there any
guidelines I should follow to avoid problems in merging? E.g. suppose I add
a button, and the new release adds a button in the same place... I'm unsure
of how merge would handle this.

Thanks !

-- 
View this message in context: http://www.nabble.com/Best-practice-for-customization-to-allow-persistance-between-versions--tp17771430p17771736.html
Sent from the Ledger SMB - Development mailing list archive at Nabble.com.