On Oct 21, 2012, at 3:12 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:

>
>
> On Sun, Oct 21, 2012 at 2:38 PM, Igor Stasenko <siguctua@gmail.com> wrote:
> On 21 October 2012 13:39, Denis Kudriashov <dionisiydk@gmail.com> wrote:
> > Hello
> >
> >
> > 2012/10/21 Igor Stasenko <siguctua@gmail.com>
> >>
> >> i now modelling a system logger (to replace .changes file), and since
> >> i having no better idea,
> >> i'll try to use object literals for it.
> >
> >
> > Do you see Deltas project?
>
> Sure i know about deltas. I was hacking it. :)
>
> > I think one of the proposals was .changes file replacement
>
> not exactly. it is more changeset replacement.
> What i am doing is a bit orthogonal: it is a facility to recover lost changes.
> All of the sources will be held inside image.
>
>
> But one very common case to recover lost changes is when the image is broken... so if you store the stuff in the image...
>

The .changes right now has two duties

1) Be a log in case of crash. Like a transaction log in a database...
2) the place where the sourcecode is because it is oh so large.

So I vote for splitting "where source is stored" from the transaction log.

The log file then will be just a log. e.g. the image that you download: the log will be empty.
The log can be deleted at any point, it is just a log.

� � � � Marcus

--
Marcus Denker -- http://marcusdenker.de