On Tue, Oct 04, 2011 at 04:15:10PM -0400, Richard Hipp wrote: > On Tue, Oct 4, 2011 at 4:09 PM, Erlis Vidal <er...@erlisvidal.com> wrote: > > > And that's what I don't understand, how could the Update "overwrote" your > > changes. > > > > This is from the update help command > > > > *Change the version of the current checkout to VERSION. Any uncommitted > > changes are retained and applied to the new checkout. > > * > > > Because of the shun, Fossil was confused. It thought that the changes had > been committed, since they had been committed immediately prior to the > shun. So the files on disk were marked as clean. Hence, Fossil overwrote > them.
Ah, I thought you had shunned the artifact of the PNG file, not that of the checkin. What would have happened, if you had removed only the artifact of the PNG? In any case, what do you think of a (at least) temporary 'fail-fast' code that will make fossil die in that unfortunate situation (the update removing files)? I'd prefer a fast abort() than the behaviour you saw. Thank you, Lluís. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
