Feb. 11, 2013
9:12 a.m.
Igor Stasenko wrote
You posed a valid question, Martin. I , personally, don't like it too, that MC logic queries all known repositories before comitting new version into any other one.
I think a mid-term solutiion for you would be to remove the remote repository from the list of project's known repositories and leave only local one. Then MC will have no reason to try accessing them.
Yes, removing the remote repository solves the problem :) Could this create a problem of conflicting "unique version number"s at a later point in time? -- View this message in context: http://forum.world.st/Problem-working-offline-with-monticello-after-project-... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.