On Tue, Sep 20, 2022 at 11:52 AM Thomas Passin <tbp100...@gmail.com> wrote:
> I'm missing some essential piece of understanding, I think. > > 1. I work on an existing external file (this is mostly what I have done). > This probably won't change LeoPyRef. I commit the changed external file > but don't commit LeoPyRef. I don't see this as needing a leoPy.leo outline > at all. > > 2. I want to add a new directory, probably with some new external files in > it. I make the changes to LeoPyRef and to my local worktree. I commit the > new directory and files, and also LeoPyRef. What problems would this > create that would be avoided by going through leoPy? > > 3. I want to add a new file to the existing directory tree; perhaps it's > a new plugin, perhaps it's a new language mode file. I commit the new > file, and I add a new subtree for it to LeoPyRef and commit that. How will > that create possible merge problems that would be avoided by making a new > LeoPyRef outline from an intermediate leoPy outline? > > I can see that there could be difficulties when one is working in one > branch and makes changes to LeoPyRef as well as changes to external files; > and then before the PR for that is merged, some other PR rom another branch > with other changes to LeoPyRef gets merged. What I don't see is how making > changes in a leoPy outline and writing a new LeoPyRef outline from it will > help with this situation. Either way, you end up with a PR that has > changes to LeoPyRef that need to be reconciled with some other PR's changes. > In practice, only a few devs mess with LeoPyRef.leo, so the suggested workflow seems to make sense, but can't guarantee the workflow is a big improvement. 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/CAMF8tS3p2CpwiQEpzu%3Dfi%3DXC4eqGNuYMdqPbkH-oxA0qVjLspQ%40mail.gmail.com.
