On 22 May 2013 10:11, Camillo Bruni <[email protected]> wrote: > > On 2013-05-19, at 03:23, Igor Stasenko <[email protected]> wrote: > >> On 18 May 2013 02:31, Camillo Bruni <[email protected]> wrote: >>> Pharo 3.0 is now properly tracked on github >>> >>> - https://github.com/pharo-project/pharo-core >>> - the update messages are properly shown >>> - html output: >>> https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf466ca53507dbafd >>> - diff output: >>> https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf466ca53507dbafd.diff >>> - patch output: >>> https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4ccf466ca53507dbafd.patch >> >> You are my hero! >> Now can we have same for VM sources? >> I would really love to simplify a process of changing VM by simply modifying >> file either on disk (in platform sources) or in image (VMMaker & friends) >> and then do >> >> git ci -m "new fix/feature integrated" > > well it works only 1 way right now. I have not implemented any mapping from > my fileformat > to monticello (even though it shouldn't be that hard).
You could take a look at Filetree's reader (MCFileTreeStReader, IIRC). Your fileout format's pretty similar. frank
