Yeah, I do use the MergeDriver and it saved me a lot of headache, but when I see things like this
https://github.com/dynacase/dynacase/commit/90141d63bfdd433e51a768c2191e035b76c5da83 where one five lines long method generated 14 file changes with 180 additions and 172 deletions... it makes the log on github and pull requests incredibly messy. I don't want to cut branch under myself if I were to remove the properties file. So my question now is: how hard would it be to regenerate those files? Or maybe if it was moved to some metadirectory. This reminds me a bit of svn which polluted the whole folder tree with .svn files everywhere. Peter On Wed, Apr 8, 2015 at 1:14 AM, Sean P. DeNigris <s...@clipperadams.com> wrote: > Dale Henrichs-3 wrote > > Personally I use > > https://github.com/ThierryGoubier/GitFileTree-MergeDriver and never > > think twice about the properties files ... > > Ooh, intriguing. In other to make it easier to view code on GitHub, I've > been toying with the idea of generating one-class-per-file in addition to > the regular gitfiletree files. Could this be used to make that possible > without complicating Git? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Metacello-GIT-methodProperties-json-tp4818097p4818233.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >
