Sorry my bad, I was confused because on the main page the footer of the page shows 1.34, but I just notice that when going inside one repository it's 1.36.
-- Martin G. Le mer. 22 févr. 2017 à 11:45, Roy Keene <fos...@rkeene.org> a écrit : > ChiselApp runs Fossil 1.36 currently, not 1.34. > > On Wed, 22 Feb 2017, Martin Gagnon wrote: > > > > > Le mer. 22 févr. 2017 à 03:33, Tony Papadimitriou <to...@acm.org> a > écrit : > > I placed some unversioned file to a chiselapp repo I maintain and > then from the Web UI tried to locate the file but without luck. > > There isn?t even a hint that some unversioned file is in the repo, so > that one can try to UNV SYNC from the command line (after cloning). > > > > Maybe the FILES tab should have an additional option (next to All, > Tree-View, etc.) for Unversioned? And from there process them (e.g., > download, hex) exactly the same. > > > > > > > > Hi Tony, > > > > To see the list of unversionned files on a repo, use the /uvlist page: > > > > example: https://www.fossil-scm.org/index.html/uvlist > > > > But in your case, I'm afraid that Chiselapp use a too old version of > fossil (1.34). unversionned files feature appear in 1.36. > > > > May be "unver sync" command could return an error in that case? > > > > Regards, > > > > -- > > Martin G. > > > >_______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users