Issue 7026 in pharo: "Changes" in Monticello seems to compare to the latest in the cache

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 7026 in pharo: "Changes" in Monticello seems to compare to the latest in the cache

pharo
Status: Accepted
Owner: [hidden email]
Labels: Type-Bug Importance-Low Milestone-2.0

New issue 7026 by [hidden email]: "Changes" in Monticello seems to  
compare to the latest in the cache
http://code.google.com/p/pharo/issues/detail?id=7026

When having a dirty package, one often wants to know "what are the changes  
to the repository".

It seems that this now now just compares to the repo but if there is a  
newer version in the cache, it
uses that (and shows that there is no change to the repository).

This is wrong.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7026 in pharo: "Changes" in Monticello seems to compare to the latest in the cache

pharo
Updates:
        Labels: -Milestone-2.0

Comment #1 on issue 7026 by [hidden email]: "Changes" in Monticello  
seems to compare to the latest in the cache
http://code.google.com/p/pharo/issues/detail?id=7026

this was like that since ages. So it will not be for 2.0


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker