On Mon, Aug 12, 2019 at 4:22 PM Brian Theado <brian.the...@gmail.com> wrote:
1. IMO, at a bare minimum, you should always first check in the pyzo code without any of your changes and only then add your changes. > IMO, at a bare minimum, you should always first check in the pyzo code without any of your changes and only then add your changes. I agree. My personal copy of the pyzo code is in pyzo.leo, in c:\apps\pyzo. It's been under git control from day 1. As you say, it would have been better to start with a clean copy in both leo/external/pyzo and leo/plugins/pyzo. When the dust clears it might be best to start completely afresh. This would make clear what has happened in the git log, and will ensure that all required changes are properly marked. But this is for later. > Git has a very useful subcommand called 'subtree' which can be used to track another repository as a subdirectory of your own repository. Thanks for this. > can...the changes you make be generalized such that they are not leo specific? Big sigh. This is a question for another day. The strategy that has just become clear probably already does that. Having said that, I'm not going to clutter my head with another constraint. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3VHNk7q2S_vY40Q0-hOW8sP%3DSaTM%3D11Yxc-8O2%3DJuYrA%40mail.gmail.com.
