On Tue, Jun 15, 2010 at 12:12 AM, Julian Fitzell <[email protected]> wrote:
> It seems that in Pharo 1.1 MC no longer displays the Version window
> after a failed commit attempt (due to missing authentication for
> example). As a result, cannot easily resubmit the version after fixing
> the credentials.
>
> In fact, as I look further, it's worse than that. Let's say I had
> version 1 and changed two methods. After the failed commit the
> following seems to be the situation:
>
> - The ancestor of my working copy is 2 instead of 1 (confirmed with History)
> - The working copy is dirty
> - The Changes button shows the same two modified methods that I was
> trying to save into 2
> - The diff between 1 and 2 shows the two modified methods
> - The diff between 2 and my image (as selected from the History
> window) shows no changes

Actually, most of the additional points are ok. The Changes button is,
of course, relative to the selected repository (I say of course, not
because that's necessarily intuitive but because I was previously
aware of it) so that's why it showed the changes still. The ancestry
information is all correct and opening up the package-cache to
resubmit the version did get me back in business.

I still think digging into the package cache to find it is not an
optimum solution to this fairly common problem, though.

Julian

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

Reply via email to