Hi Arnold, On Sat, Nov 26, 2016 at 01:15:11PM +0100, arnoldemu wrote: > Hi, > > I submitted a change and made a mistake in the comment. > I wanted to change the comment and fix it. > > I did this: > > fossil amend ba67fcd67c -m "fixed snapshot" > > command reported the comment, tags and uuid. > > fossil changes showed nothing.
Normal, the amend command works directly on the repository, not on the checkout. So it's true that nothing have change on your checkout. > > I looked at the server and there was no changes. But on your local repository, if you do "fossil ui" or "fossil timeline", you will see the changes. > > I forced a submit with > > fossil commit --allow-empty > > and it appears to have worked. Server get the change here, because the "commit" command does a "sync" when autosync is enable (which is the default). > > I wish "fossil changes" would list this change (and changes like > changing file type) because it's confusing that some changes are > listed and some are not. > I should then just be able to submit without forcing. The way I see it > is I did make a change, so it should be listed and the commit is not > empty. > The command you should have done to send this change to the server is "fossil sync" or "fossil push". I agree that it can be confusing that the "amend" command doesn't listen to the "autosync" setting, like "commit". But it would have been the same if you had edited the comment from web interface using "fossil ui". I'm not sure if I want my "fossil ui" edit's to automatically call sync. Especially when the edits is done in many steps. I feel a little bit the same about the amend command. Someone else have any thought about this ? -- Martin G. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
