Richard Hipp wrote: [...] > It is hard-coded C logic. > > Any given file might have multiple file sizes, since the file size > typically changes at each check-in. Which file size were you interested > in seeing?
The most common use case would be when viewing files for a particular checkin, branch or for tip, so the most recent revision for the checkin would be the obvious choice. I've found the code that actually generates the list; it's pretty simple and looks easy to tweak. Would there be any interest in my trying to do this properly via a TH1 script? -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ "Parents let children ride bicycles on the street. But parents do not │ allow children to hear vulgar words. Therefore we can deduce that │ cursing is more dangerous than being hit by a car." --- Scott Adams
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
