Re: [fossil-users] Fossil Version 2.1 (prerelease)

2017-03-06 Thread Warren Young
On Mar 5, 2017, at 9:15 AM, Richard Hipp wrote: > > On 3/5/17, Lonnie Abelbeck wrote: >> fossil init --sha1 repo.fossil > > why would you want to do that? One may have a public-facing repo and want it to be readable by the fossil binaries packaged

Re: [fossil-users] Fossil Version 2.1 (prerelease)

2017-03-05 Thread K. Fossil user
fossil-users] Fossil Version 2.1 (prerelease) On Mar 5, 2017, at 10:15 AM, Richard Hipp <d...@sqlite.org> wrote: > On 3/5/17, Lonnie Abelbeck <li...@lonnie.abelbeck.com> wrote: >> For what is planned for Fossil 2.1, will new repos created using 2.1 using: >&g

Re: [fossil-users] Fossil Version 2.1 (prerelease)

2017-03-05 Thread Lonnie Abelbeck
On Mar 5, 2017, at 10:15 AM, Richard Hipp wrote: > On 3/5/17, Lonnie Abelbeck wrote: >> For what is planned for Fossil 2.1, will new repos created using 2.1 using: >> -- >> fossil init --sha1 repo.fossil >> -- >> be compatible with recent Fossil 1.x

Re: [fossil-users] Fossil Version 2.1 (prerelease)

2017-03-05 Thread Richard Hipp
On 3/5/17, Lonnie Abelbeck wrote: > For what is planned for Fossil 2.1, will new repos created using 2.1 using: > -- > fossil init --sha1 repo.fossil > -- > be compatible with recent Fossil 1.x versions ? Yes. But why would you want to do that? Fossil 2.0 is out and

[fossil-users] Fossil Version 2.1 (prerelease)

2017-03-05 Thread Lonnie Abelbeck
For what is planned for Fossil 2.1, will new repos created using 2.1 using: -- fossil init --sha1 repo.fossil -- be compatible with recent Fossil 1.x versions ? Ref: Add the --sha1 option to the "fossil new" command, to simplify the creation of new SHA1-only repositories.