On Mar 9, 2017, at 2:59 PM, Richard Hipp <[email protected]> wrote: > > The "fossil new" command creates an initial, empty check-in which is > suppose to become the ancestor of all future check-ins. That check-in > will have a SHA3 hash, unless you use the --sha1 option on "fossil > new”.
Maybe then just a notice in Admin > Configuration or similar: “Hey, you know you’ve got a repo that Fossil 1.x can’t read, right? Just checking.” _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
