I came here to recommend "script tracker" as a powerful tool for those storing stacks in vcs. In the end it all depends on how your workflow is going to happen. Are you going to do merges? If that is the case then you need to plan ahead and carefully since you can't merge binary stacks. Another potential solution is any of the old school vcs in which you "checked out a file" and locked other people from changing it. This way, it becomes easier to work with binary files as there is never a merge (or there shouldn't be). There used to be a really nice tool supporting this use case by Chipp Walters called Magic Carpet. I used to make very good use of it for working. I wonder if Chipp still here and if he'd consider releasing that as FOSS.
On Fri, 24 Apr 2020 at 05:11, Mark Wieder via use-livecode < firstname.lastname@example.org> wrote: > On 4/23/20 9:04 PM, Brian Milby via use-livecode wrote: > > New dedicated repo is located at: > > https://github.com/bwmilby/scriptTracker > > Oh, cool. I'll change my git remote. > > -- > Mark Wieder > ahsoftw...@gmail.com > > _______________________________________________ > use-livecode mailing list > email@example.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- http://www.andregarzia.com -- All We Do Is Code. http://fon.nu -- minimalist url shortening service. _______________________________________________ use-livecode mailing list firstname.lastname@example.org Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode