Quoting Eliot Miranda <eliot.miranda at gmail.com>: 

> On Thu, Nov 21, 2013 at 4:52 PM, Igor Stasenko <siguctua at gmail.com> wrote:
>
>
> > On 21 November 2013 02:14, J. Vuletich (mail lists) <juanlists at jvuletich.org> wrote:
> >
> >
> > > There is a simpler way, using Git as it is meant to be used. Take a look at https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/commit/3deff0d7b9707258766d6f003b783077664a4023#diff-5fe4c9854ae64b52029283e0648affd4 . We've been using this for a couple of years, and it works nicely.
> >
> >
> > This is simpler, yes, but much less integrated than filetree.
> >
> > Because having separate file per method, means git can produce proper diff on a per-method basis, while if you just store fileouts, git can often give you false diffs
> >
> > (try changing order of methods fileout which will turn whole diff to be red/green,
> >
> > while there could be no changes at all).
>
> And the fact that git requires one file per method to generate proper diffs is my #1 reason for wanting /not/ to use a file-oriented SCM for Smalltalk.

But that's not true, as I just answered Igor. All that is needed is to save stuff in package files in a well defined order, as Cuis does.

> I can only conclude that put up with the line-oriented diffs that git/subversion/mercurial/sccs/rcs/cvs produce is that the macro preprocessor in C and C++ makes it impossible in general to derive the structure of C and C++ programs form their source.  You yourself, Igor (and I agree with you except that a macro system is very useful) were complaining about how awful the C.C++ macro system is (and it is).  hat a mad world we live in :-).  
>
> --
> best, 
> Eliot

Cheers,
Juan Vuletich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131121/fa625933/attachment.htm