I recently isolated a regression in baz-1.3, 1.3.1 and COTM: In some circumstances, baz update will only update the patchlogs, that is it will regress to "sync-tree".
https://launchpad.ubuntu.com/malone/bugs/384 Effectively, that makes the tree look like it is up to date without changing any source file. If you commit such a tree, that will actually revert the changes that update should have applied. Until that is fixed, please be very careful when using "baz update". 1. Start with "baz status" to make sure your tree has not uncommited changes. 2. Do "baz update" 3. Do "baz status" again to make sure the update went correctly. 4. If any uncommited changes appear, you tripped on the bug, run "baz undo -nq" to complete the update operation. The builder, replay, merge and apply-delta did not appear to be affected with the problem during my tests. -- -- ddaa
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
