Hi! 

> Am 10.09.2017 um 05:44 schrieb Alexandre Bergel <alexandre.ber...@me.com>:
> 
> Hi! 
> 
> I live very very much this idea!
> 
> I am wondering why do we need the timestamp? Git knows about who has 
> committed each line and by whom. Why should we have some redundant 
> information?
> 
the difference is commit time vs. compile time. From a collaboration point of 
view it is the important time. From a personal view it might do a service to 
have the date you compiled. But putting the timestamp where git will resolve a 
conflict is a no-go. Everyone who used filetree with metadata can tell it is 
super annoying and destroys the complete experience. 

Norbert
> Cheers,
> Alexandre
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
>> On Sep 9, 2017, at 6:39 AM, Esteban Lorenzano <esteba...@gmail.com> wrote:
>> 
>> 
>>> On 8 Sep 2017, at 22:02, Eliot Miranda <eliot.mira...@gmail.com> wrote:
>>> 
>>> Hi All,
>>> 
>>>> On Sep 8, 2017, at 9:44 AM, Stephane Ducasse <stepharo.s...@gmail.com> 
>>>> wrote:
>>>> 
>>>> Hi all
>>>> 
>>>> At ESUG we discussed with Esteban, martin mcClure, Dale and (many many
>>>> others :), esteban designed a nice class file format. So that we will
>>>> not have 2Gb of space on harddisc, problems with long method names and
>>>> sluggish commits.
>>> 
>>> Wow, that's great news!  It'll make it much easier to import from Pharo hit 
>>> repositories.  Thank you, Esteban!  
>>> 
>>> Can someone post the grammar or a description of the syntax asap?
>> 
>> I will commit it with a spec next week. 
>> and I made the parser by hand and simple enough (e.g. I didn’t use RBParser) 
>>  so it can be ported easily to other dialects. 
>> 
>> Esteban 
>> 
>>> 
>>>> 
>>>> He is waiting at Wien and is probably checking everything right now.
>>>> 
>>>> It is a nice format because we will be able to use it to communicate
>>>> by emails using it. So readable, compact and I like it :)
>>> 
>>> Lovely!  Details please :-)
>>> 
>>>> 
>>>> Stef
>>>> 
>>> 
>> 
>> 

Reply via email to