> On Aug 22, 2017, at 9:39 AM, Drew Waddell via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Yeah, it's incredibly noisy but we only keep the information around for a > release, then we fire up a new Git repo for the next one. Like I said it's > not perfect, far from it honestly, but it gives us something which is more > than what is currently capable in native 4D.
The idea of committing every method change and especially creating a new repo for releases seems to be totally contrary to what git should be used for. I only commit method changes to git when I make a new release. This is the only effective way to track down problems between released versions. John DeSoi, Ph.D. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
