On 8/30/2016 1:55 PM, Ron W wrote:
Why only "sync -u" ?
Probably to give an easy way to distinguish developer's clones from full mirrors. If the unversioned files are built releases, then I don't need them on my dev machine, so no reason to sync them.
If unversioned files are used for something else, syncing them might make more sense.
It might also make more sense for that to be controlled by a setting rather than a command line option to fossil sync. I'm not sure about that, without thinking through other use cases.
On Tue, Aug 30, 2016 at 2:31 PM, Richard Hipp <d...@sqlite.org <mailto:d...@sqlite.org>> wrote: A new feature of Fossil (currently unreleased and only available to people who are willing to recompile the code on trunk) is "unversioned files". ....
-- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ +1 626 303 1602 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
