two things:
1.
in autosync mode, one can do `fossil up' to pull/push changes and
integrate them into the checkout which mostly prevents unnecessary forking
etc. this is (for good reason) listed as one notable advantage of `fossil'
over other DVCSs.
however, (local) changes to the wiki pages are ignored by `fossil up',
i.e. are not propagated to the remote repo. o.t.o.h. after `fossil ci' the
wiki changes _are_ propagated, together with the checked-in (file-)
modification.
but w/o doing a checkin, in order to actually sync the wiki changes, I
have to issue `fossil sync, fossil up' (the latter to integrate remote
changes into the checkout).
question: should not `fossil up' also honor wiki edits (and tickets,
events), too, in autosync mode?
the present behavior (`up' ignores wiki, `ci' syncs wiki changes, too)
feels a bit inconsistent (not claiming that it really is...).
2.
`fossil help up' does not include any information what happens (and what
not) in autosync mode (neither to files, nor to wiki edits etc), but it
should.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
