-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This probably isn't news to anyone, just a gotcha that I ran into, and not for the first time. Figured I'll describe it on the list and see if anyone has any thoughts. This isn't a bug or anything; Fossil is behaving according to design. It's just a surprise due to not paying complete attention to what's really going on.
The other day I did [fossil update] in my SQLite trunk checkout, got version [c6399958]. Today I did [fossil update] and stayed at the same version despite pulling many artifacts. [c6399958] started life on trunk but later moved to a branch, so my update kept the checkout on the branch. The record shows that [c6399958] inherits sym-tkt-2326c258 from [c0f4e308], which was added by [1e3cf43e] a minute after [60161b5f] updated the comment to say that the change isn't a complete fix. My naïve user perspective is that I started on trunk and therefore every update should keep me on trunk. But that's not the full story since the checkout version's branch can be edited. If I don't pay close attention to changes in branch, I will be surprised when my future updates stop "doing" anything. - -- Andy Goth | <andrew.m.goth/at/gmail/dot/com> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJU9fiAAAoJELtYwrrr47Y4PkQH/i//B8un6qs9KVvMwX4IIh4v NmXU0Z6+XqWDGEXDMtEj4JFzYvfckMzStc1xFOnedZbKr02Hyix1L25ZcTtcDWBe YB2Fb9iVzupyLUQ6QoWwA1dUQQJi3GDHEpY/h7sjgW/Cx3bs41iRaB3RTrTiShrl EhTIcuyKD2ClV/+lxXQxcIloamb/S1JdEIpwYjLro+K8/n7LHZTFTFKHe2+5kz9J deM9OAg4dbq4h5cMK4IyOQ/sD/wHCJGjpMPHI69ii8UKXcqAOw4apWo0e74hTJmP LhBdjZwt2XgrFLuHNa6rx+ztQDoci/E8+56YSkw/N4/sGDvi8OI5gb0JSMmGrvY= =JLsE -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
