On 3/9/17, Warren Young <[email protected]> wrote: > On Mar 9, 2017, at 2:54 PM, Richard Hipp <[email protected]> wrote: >> >> On 3/9/17, Warren Young <[email protected]> wrote: >>> Our newbie may be setting up a repo that >>> they know needs to be accessible to Fossil 1.x clients, and they can’t >>> force >>> the upgrade. >> >> Our newbie is going to need to know about the --sha1 option to "fossil >> new". > > You’re saying that if I init a repo in SHA3 mode, then open it and > immediately go into Fossil UI, it’s already too late to change the hash > policy? > > I thought it wouldn’t be too late until the first commit happened. > > Is it because of the initial empty commit?
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". And once you get one SHA3 artifact in the repo, legacy clients cannot handle it. -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
