On 16 September 2015 at 05:16, Scott Robison wrote:
> On Tue, Sep 15, 2015 at 7:46 PM, Warren Young wrote:
>>
>> On Sep 15, 2015, at 7:01 PM, Scott Robison
>> wrote:
>> >
>> > I think calling it a non sequitur is not completely
On Wed, Sep 16, 2015 at 1:38 AM, Stephan Beal wrote:
> (i will naively assert) "impossible" that both the sha1 and md5 could
> both be made to match in a collision of a non-empty blob.
This might be too optimistic. According to Antoine Joux in
"Multicollisions in Iterated
On 9/16/15, Noam Postavsky wrote:
> On Wed, Sep 16, 2015 at 1:38 AM, Stephan Beal
> wrote:
>> (i will naively assert) "impossible" that both the sha1 and md5 could
>> both be made to match in a collision of a non-empty blob.
>
> This might
On Sep 16, 2015 3:24 AM, "Michal Suchanek" wrote:
>
> On 16 September 2015 at 05:16, Scott Robison
wrote:
> > But GPG could solve any weaknesses with Fossil's use of SHA-1, though.
It
> > won't prevent a determined party from deconstructing a repo,
On Tue, Sep 15, 2015 at 9:24 PM, The Tick wrote:
>
>
> That is one of the features that I was looking for. How to get the URL for
> that to put on the 'home' page is one of my next tasks. I doubt that most
> windows users would explore fossil's interface (and understand it
Hi. I pushed http://fossil-scm.org/index.html/info/533f8b6aeacb554f on its
own branch for review (philosophical/ui, or errors/updates); otherwise,
it's ready for integration.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
https://www.youtube.com/watch?v=W71BTkUbdqE
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Isn't the main annoyance the need to commit two times, one in nested checkout
and one in the 'root' repo, and to try to keep timeline order in both?
How do you guys manage that - prevent committing/cloning to root and always use
sub-repos?
Original Message
From: Warren Young
Sent: Tuesday,
On Sep 16, 2015, at 12:13 PM, Scott Robison wrote:
>
> https://www.youtube.com/watch?v=W71BTkUbdqE
The point I took from that that seems most applicable to Fossil is the idea
that “workspaces” (i.e. local clones) are not complete copies of the entire
repo’s history.
Thus said Oliver Friedrich on Sat, 12 Sep 2015 12:34:21 -:
> What I really would like to have is to gather multiple such small
> projects in one repo file, so instead of having one ROOT check-in,
> having one ROOT for each project. I know that would make developing
> fossil a bit
On 16 September 2015 at 21:56, Steve Stefanovich wrote:
> Isn't the main annoyance the need to commit two times, one in nested
> checkout and one in the 'root' repo, and to try to keep timeline order in
> both?
>
> How do you guys manage that - prevent committing/cloning to root
11 matches
Mail list logo