Anonymization is not possible because the user name is part of each commit entry, which means that it affects the hash code of each commit. Changing any data in a commit, including the user name or timestamp, would change the hash, and thereby invalidate every commit which derived from that. Fossil, by design, cannot modify historical data.
----- stephan Sent from a mobile device, possibly left-handed from bed. Please excuse brevity, typos, and top-posting. On Tue, May 15, 2018, 16:59 Peter Vonča <pvo...@gmail.com> wrote: > I understand, how about anonymization then. User "Jane" is deleted. > Replace all references with default user "Anonymous". > > > > > On Tue, May 15, 2018 at 12:41 PM, Victor Wagner <vi...@wagner.pp.ru> > wrote: > >> On Tue, 15 May 2018 12:34:07 +0000 >> Peter Vonča <pvo...@gmail.com> wrote: >> >> > Is there a practical reason why users can't be deleted or was it just >> > a design decision? I guess if I stop fossil server I can manually >> > edit the sqlite db and delete from table? >> >> Fossil keeps history forever. How would it do so, if author of some >> commits or wiki edits disappears from the repository completely. >> >> Disable access, revoke privileges, but keep the user in the DB, >> because it has log of his activity. >> -- >> _______________________________________________ >> 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 >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
