fossil checkoutaborts if there are changed files in the local directory unless you give the
fossil updatemerges upstream changes with your local changes. Since Fossil tends to follow the CVS command design, and CVS popularized the merge on update workflow, we expect that Fossil’s update behavior is more likely to be what you want.
Update triggers an autosync attempt; checkout does not.
Several features in
fossil updatedo not exist in
fossil checkout, so developing a habit to type
fossil upmeans you’re more likely to have the features you want at hand.
fossil checkout --keepfeature doesn’t exist in
fossil update, but it’s a rarely-needed operation, so it doesn’t provide a good reason to develop a habit of using
In summary, these are two separate commands; neither is an alias for the
other. They overlap enough that they can be used interchangeably for
some use cases, but
update is more powerful and more broadly useful.