kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

>
>     Was thinking you would maintain a full hg python tree, with the CMake stuff in there all
>     the time.
>     This way you can pull from upstream, and generate a diff which constitutes the CMake
>     patch
>     at any time.
>
>     The form of David's work now is actually pretty inconvenient to use, since:
>
>     a) it is not actually a patch but rather an overlay.
>     b) he makes the mingw stuff optional, and it should not be.
>
>     In your shoes I would maintain a full separate python tree in hg, say perhaps on google
>     code if they support hg.
>
>
>
> Another DVCS system? (waaahhhh)... ';-)


http://wiki.bazaar.canonical.com/BzrMigration#Mercurial_.28hg.29

Dude, never swim upstream when you don't have to.