switching to metadata-less gitfiletree

> Hi,
>
> I've followed this thread
> http://forum.world.st/How-do-I-convert-a-FileTree-project-to-Metadataless-GitFileTree-project-td4903920i20.html
> to switch to metadata less format,
>
> Specifically:
>
> 1. change `.filetree` file, 2. load the repo to a clean image 3. make
> a change to each package and commit it
>
> This worked correctly, however having to recommit each package is
> annoying if there are several.

> Hi Peter,
>
> Le 29/07/2016 à 18:05, Peter Uhnak a écrit :
> > Hi,
> >
> > I've followed this thread
> > http://forum.world.st/How-do-I-convert-a-FileTree-project-to-Metadataless-GitFileTree-project-td4903920i20.html
> > to switch to metadata less format,
> >
> > Specifically:
> >
> > 1. change `.filetree` file, 2. load the repo to a clean image 3. make
> > a change to each package and commit it
> >
> > This worked correctly, however having to recommit each package is
> > annoying if there are several.
>
> the "resaving" thing isn't necessary. It would have happened anyway on the
> next save for a package, and gitfiletree never reads the metadata anyway.
>
> > My question is:
> >
> > * is it safe to directly remove the incriminating files (all
> > monticello.meta/version & methodProperties.json files),
>
> Yes. You could also ask git to ignore them (some do that :)).
>
> > * is it possible to mass-commit all packages with simple script,
>
> Yes.
>
> > * or should I just ignore the metadata and eventually someone will
> > make  a change to the package so the metadata silently disappears?
>
> You could ignore, yes.
>
> I'd choose ignoring. Once the property (metadata-less) is set on the
> repository, it is kept and maintained. Just don't forget to commit it :)
>