On Tue, Oct 28, 2014 at 7:31 PM, B Harder wrote:
> That said -- I would like an option to "pop and discard" from a branch
> tip. Possible? If the repo has been sync'd, then that work would come
> back to you on next sync (that's understood), but if it hasn't been
> sync'd, it could be useful.
>
On Tue, Oct 28, 2014 at 6:31 PM, B Harder wrote:
> That said -- I would like an option to "pop and discard" from a branch
> tip. Possible? If the repo has been sync'd, then that work would come
> back to you on next sync (that's understood), but if it hasn't been
> sync'd, it could be useful.
>
On 10/28/14, Jungle Boogie wrote:
> Dear Richard,
>
> From: Richard Hipp
> Sent: Tue, 28 Oct 2014 10:09:25 -0400
> To: Fossil SCM user's discussion
> Subject: Re: [fossil-users] Fossil checksum
> >
>> On Tue, Oct
On Tue, Oct 28, 2014 at 1:10 PM, Jungle Boogie
wrote:
> Is there a way to delete the commits and any traces of it?
>
https://www.fossil-scm.org/fossil/doc/trunk/www/shunning.wiki
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossi
Dear Richard,
From: Richard Hipp
Sent: Tue, 28 Oct 2014 10:09:25 -0400
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Fossil checksum
>
On Tue, Oct 28, 2014 at 10:00 AM, Stephan Beal
wrote:
i don't remember any numb
On Tue, Oct 28, 2014 at 3:51 PM, Gour wrote:
> On Tue, 28 Oct 2014 10:09:25 -0400
> Richard Hipp wrote:
>
> > That same commit rate will cause Fossil to exceed its maximum
> > repository size (140 terabytes) in about four minutes.
>
> What now?
>
At that point we would ask the owners of that db
On Tue, 28 Oct 2014 10:09:25 -0400
Richard Hipp wrote:
> That same commit rate will cause Fossil to exceed its maximum
> repository size (140 terabytes) in about four minutes.
What now?
Sincerely,
Gour
--
The spirit soul bewildered by the influence of false ego thinks
himself the doer of ac
On Tue, Oct 28, 2014 at 10:00 AM, Stephan Beal
wrote:
> i don't remember any numbers from that thread, but do remember one quote.
> When (whoever it was, probably Richard) explained that The Math shows that
> a collision is not likely to happen until some tens of thousands of years
> in the futur
On Tue, Oct 28, 2014 at 2:42 PM, Baruch Burstein
wrote:
> If it is sha1, are there plans to switch to sha256?
>
>
> I am not an authority on fossil roadmap, but I would guess that there is
> no such plan. Why switch? the hashes are not used for security, but as a
> type of checksum. The chance of
On Tue, Oct 28, 2014 at 3:09 PM, Jungle Boogie
wrote:
> From what I've read regarding the fossil documentation, it seems that sha1
> hashes are used for the files. Is that still correct?
>
Yes
> If it is sha1, are there plans to switch to sha256?
I am not an authority on fossil roadmap, but
Hello All,
From what I've read regarding the fossil documentation, it seems that sha1
hashes are used for the files. Is that still correct?
If it is sha1, are there plans to switch to sha256?
Thanks!
--
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
__
11 matches
Mail list logo