I think you took a look at a larger change, not the one from
Guillermo. What you see is a change which has been deleted for Moose 4.1. The comment is
meant to say this attribute is always nil and hence useless as the importer does not care
about setting a container for unknown variables. And since nobody ever complained about a
container set to nil, I assume nobody needs container on FamixUnknownVariable. We can
always add it later.
Oh...sorry then... I did just a diff from the actual code and the version 123.
> On 11 Oct 2010, at 09:32, Simon Denier wrote:
>> Hi Guillermo
>> I saw your commit and especially your comment
>> "saving locally first, then remotelly, doesn't simply copy the changes
like Mercurial does..."
>> The way it works with Monticello, compared to Git/Mercurial (remember that
Monticello was conceived before/in parallel with such systems...)
>> - the save command in MC always creates a new version of your package in the
repository you selected
>> - saving a version on a remote repository also saves a local copy
>> - if you want to save a version first locally, then want to copy it later to
another repository, use the "copy" command from the MC browser
>> Alternatively, the Gofer API provides commands which are closes to Git/Mercurial
workflows: push/fetch etc.
>> See http://www.lukas-renggli.ch/blog/gofer
>> BTW, is the fix complete? Your package only provides a new method
>> Moose-dev mailing list
> Alexandre Bergel http://www.bergel.eu
> Moose-dev mailing list
Moose-dev mailing list
Alexandre Bergel http://www.bergel.eu