Got it. Thank you again and have a nice day!
With best regards,
Orzech
Dnia 12 marca 2017 19:54 Richard Hipp d...@sqlite.org napisał(a):
It will be inferred the first time you push a new SHA3 commit.___
fossil-users mailing list
On 3/12/17, Piotr Orzechowski wrote:
> What should I do to make my existing repositories default to SHA-3?
> Should I set this hash-policy to sha3 on my server-side repositories too
> or maybe it will be inferred default after first SHA-3 commit pushed to
> them?
It
What should I do to make my existing repositories default to SHA-3?
Should I set this hash-policy to sha3 on my server-side repositories too
or maybe it will be inferred default after first SHA-3 commit pushed to them?
Regards,
Orzech
Dnia 12 marca 2017 19:22 Richard Hipp d...@sqlite.org
On 3/12/17, Piotr Orzechowski wrote:
>
> So active checkout must have this setting set, but clones created with
> Fossil 2.1 will use SHA-3 by default?
No. If you create a new repository with 2.1, then it will use SHA3 by
default. But existing repos will continue to
Thank you very much!
So active checkout must have this setting set, but clones created with Fossil
2.1 will use SHA-3 by default?
With best regards,
Piotr
Dnia 12 marca 2017 18:50 Richard Hipp d...@sqlite.org napisał(a):
On 3/12/17, Piotr Orzechowski fossi...@orzechowski.tech wrote:
Can I
jump
On 3/12/17, Piotr Orzechowski wrote:
> Can I
> jump directly from 1.37 to 2.1?
Yes. Simply download and install 2.1 and you are done.
Optional seconds step: Type "fossil hash-policy sha3" in a check-out
directory of any repository that you want to start using SHA3
Hello,
thank you very much for this release. I have few self-hosted
repositories that only I contribute to. What is my upgrade path? Can I
jump directly from 1.37 to 2.1? Do I have to rebuild repositories,
should I or maybe could I with some benefits?
With best regards,
Orzech
On Sun, Mar 12, 2017 at 5:21 PM, Clifford Yapp wrote:
> I know the libfossil project has been on hold, but I was curious if
> anyone can offer some insights on a) what work is still "left to do"
> on libfossil to make it a ready-to-use product, and b) whether there
> is a
I know the libfossil project has been on hold, but I was curious if
anyone can offer some insights on a) what work is still "left to do"
on libfossil to make it a ready-to-use product, and b) whether there
is a lot of work to do to update it based on the new 2.x releases?
Thanks,
CY
9 matches
Mail list logo