On Mar 9, 2017, at 3:00 PM, Warren Young <[email protected]> wrote: > > 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.”
It could be conditional based on the repository age, disappearing after a week or a month. And the code to generate it can be removed once Fossil 2.x is old enough that the chances of running into Fossil 1.x is tiny. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
