On Mon, Aug 27, 2018 at 2:50 PM Terry Brown wrote:
> On Mon, 27 Aug 2018 10:55:13 -0700 (PDT)
> Phil wrote:
>
>
>
> I'd do something like this:
>
All excellent advice. The local .leo file need not ever be in sync. Being
able to add new files from the plugin or a button makes a lot of sense.
On Mon, 27 Aug 2018 10:55:13 -0700 (PDT)
Phil wrote:
> Thanks for that, it's helpful. But the notion of a reference file
> begs the question of who maintains *that* file. In my project, both
> my partner and I are continually creating new content, which means
> that we would both need to make
On Mon, Aug 27, 2018 at 12:55 PM Phil wrote:
> Thanks for that, it's helpful. But the notion of a reference file begs the
> question of who maintains *that* file. In my project, both my partner and
> I are continually creating new content, which means that we would both need
> to make changes to
Thanks for that, it's helpful. But the notion of a reference file begs the
question of who maintains *that* file. In my project, both my partner and I
are continually creating new content, which means that we would both need
to make changes to the reference file. This impedes the efficiency
On Mon, Aug 27, 2018 at 10:19 AM Phil wrote:
> I am currently collaborating on a project with one other person, using Leo
> and Git. In addition to committing derived files to Git, we have also been
> committing the Leo file itself. We have had some occasional problems (a
> corrupted Leo file,
I am currently collaborating on a project with one other person, using Leo
and Git. In addition to committing derived files to Git, we have also been
committing the Leo file itself. We have had some occasional problems (a
corrupted Leo file, mainly), making me think that we should *not* put the
