On 13 January 2018 at 04:50, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:

2018-01-12 21:23 GMT+01:00 Norbert Hartl <norbert@hartl.name>:
Don��t you think having Author and timestamps is important?

Glad to see Pharo Community waking up :)
I felt a bit alone since I complained about that in last November ('about SortFunctions' thread)

I've recently started using Pharo 7 and found it disconcerting when troubleshooting��

not knowing how old a method is or have any hint who might be familiar with it.

IIUC the loss of author/timestamps is a consequence of merge conflicts in version information.

I don't have a good grasp of the background on this though.�� I can't remember seeing a reproducible use case��

presented to the community to solve.�� Probably I was too busy and missed the discussion.�� Could someone

link to a past steps to reproduce?�� Or now we have new Tonel files, how we can reintroduce version info code��

into a branch so we can experiment with solutions?

I had a vague idea��where version-info was kept in a separate file to the Tonel file.

Each time the Tonel file is updated, its associated version-info is written to a *new* file.

The hash of the Tonel file would form part of the version-info filename so you can��

always find the version-info file for a given Tonel file if they become separated.

This might avoid version conflicts since whole version-info files are never modified, only deleted and added.

cheers -ben

> Am 12.01.2018 um 10:26 schrieb Stephane Ducasse <stepharo.self@gmail.com>:
>
> Hi torsten
>
> we have a super long list of *important* fixes and enhancements to do.
>
> Stef
>
>> On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares@gmx.de> wrote:
>> Not having timestamps/authors in Pharo 7 due to git and missing blame support
>> (see [1]) has other bad side effects:
>>
>>
>> - it clobbers all method stamps in an MCZ package [1] if you use Monticello
>>�� which can lead easily to trouble/lamenting
>>
>> - it is not possible to fileout a changeset [2] in the ChangeSorter
>>
>> Was there any further discussion/decision for P7 on solving this
>> or adding blame support?
>>
>> Thx
>> T.
>>
>>
>> [1] http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html
>> [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018-January/026350.html
>> [3] https://pharo.fogbugz.com/f/cases/20951/
>>