On 9/15/2015 6:09 PM, Ron W wrote:
On Tue, Sep 15, 2015 at 6:18 PM, The Tick > wrote:
However, if I do that, then the image would be included in the
project download, right? I guess one small image would not be that
big a deal, but it would
On Wed, Sep 16, 2015 at 3:01 AM, Scott Robison
wrote:
> cryptographic security, it was designed to take a blob of data and create
> a pseudo-random looking string of 40 hex digits that would be highly
> unlikely to collide with anything being done by anyone else.
>
To
In the admin pages you can change that to use your "home" wiki page (i do
that so that my repos all have the same home path).
- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Sep 16, 2015 12:09 AM, "The Tick" wrote:
On Wed, Sep 16, 2015 at 1:05 AM, Warren Young wrote:
> On Sep 14, 2015, at 11:53 PM, Stephan Beal wrote:
> >
> > it is not possible to change the hash without a near-complete overhaul
> of fossil (and its docs)
>
> I’ve already addressed the
On Sep 15, 2015, at 7:01 PM, Scott Robison wrote:
>
> I think calling it a non sequitur is not completely fair
Stephan stated that Fossil isn’t doing cryptography, therefore SHA-1 doesn’t
have to be replaced. Cryptography and message authentication are not the same
On Sep 15, 2015, at 8:18 PM, Richard Hipp wrote:
>
> what problem would you solve by changing Fossil
> to use the latest wizbang cryptographic hash function?
All I’m pointing out here is that we will shortly get to the time where it is
economically feasible to forge arbitrary
On Sep 14, 2015, at 11:53 PM, Stephan Beal wrote:
>
> it is not possible to change the hash without a near-complete overhaul of
> fossil (and its docs)
I’ve already addressed the documentation/UI issue repeatedly above: The fact
that Fossil uses SHA-1 should be a hidden
On Tue, Sep 15, 2015 at 5:05 PM, Warren Young wrote:
> On Sep 14, 2015, at 11:53 PM, Stephan Beal wrote:
> >
> > it is not possible to change the hash without a near-complete overhaul
> of fossil (and its docs)
>
> I’ve already addressed the
On 9/15/15, Warren Young wrote:
>
>> It is more likely to detect accidental corruption than deliberate
>> corruption.
>
> I thought that’s what the MD5 bits were for.
>
MD5 is 128 bytes versus 160 for SHA1. That's why I picked SHA1.
Tell me: suppose tomorrow somebody
On Tue, Sep 15, 2015 at 6:18 PM, The Tick wrote:
>
> I did run across a way to embed an image that is checked in as part of a
> project:
> http://stackoverflow.com/questions/3982999/fossil-how-to-display-checked-in-image-files-on-wiki-pages
>
> However, if I do that, then the
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 fair
>
> Stephan stated that Fossil isn’t doing cryptography, therefore SHA-1
>
On 9/15/2015 4:00 PM, Ron W wrote:
On Tue, Sep 15, 2015 at 3:54 PM, The Tick > wrote:
After starting 'fossil ui', I go Admin->Configuration
The Index page value has the suggestion to use '/home'. I did that.
Now, how do I create this
This is my first open source project... I think fossil is the easiest
source control for me to use, but I've got a lot to learn.
I've not found a way to put an image in the home page for a project.
I did run across a way to embed an image that is checked in as part of a
project:
Don't know if related, but I've also got unexpected results when subsequently
merging cherrypick merges:
http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg21107.html
(I need to come up with reproducible fossil example like you, but perhaps the
description of the problem as
What are the items that are used to calculate the hash? Is the
hash salted?
Scott Doctor
sc...@scottdoctor.com
--
On 9/14/2015 10:53 PM, Stephan Beal wrote:
On Mon, Sep 14, 2015 at 7:46 PM, Warren Young
> wrote:
On Tue, Sep 15, 2015 at 8:28 AM, Scott Doctor wrote:
>
> What are the items that are used to calculate the hash? Is the hash salted?
For files/blobs, only their content is hashed (their name/timestamp/etc.,
if any, is not used). No salt is used. If i'm not mistaken (but
Hello,
TL;DR: One-line patch seems to fix it:
--- db.c.orig 2015-09-14 20:14:25.324662150 -0500
+++ db.c2015-09-14 20:17:01.742666003 -0500
@@ -2015,7 +2015,7 @@
if( zDefault==0 && pSetting && pSetting->def[0] ){
z = fossil_strdup(pSetting->def);
}else{
- z =
On 9/15/15, Jonathan Hankins wrote:
> Hello,
>
> TL;DR: One-line patch seems to fix it:
Thanks. I checked in a slightly different change.
https://www.fossil-scm.org/fossil/info/868404c0a3adc017
>
> --- db.c.orig 2015-09-14 20:14:25.324662150 -0500
> +++ db.c
> The merge algorithm does *not* consider cherry-picks. It looks for
> the most recent common ancestor without taking cherry-picks into
> account.
Another popular version control tool whose name I won't mention (hint: rhymes
with "zit") behaves identically to fossil in this scenario. Is there
On 9/15/15, Eric Rubin-Smith wrote:
>
>> The merge algorithm does *not* consider cherry-picks. It looks for
>> the most recent common ancestor without taking cherry-picks into
>> account.
>
> Another popular version control tool whose name I won't mention (hint:
> rhymes with
a sideways question on this topic. Assume in my C editor I run
the code formatter operation which indents and parses certain
tokens for cosmetic, but not functional, changes in the file. By
parsing I mean operations such as adding/removing linefeeds
before/after a token such as a bracket or
On Tue, Sep 15, 2015 at 2:34 AM, Stephan Beal wrote:
>
> For files/blobs, only their content is hashed (their name/timestamp/etc.,
> if any, is not used). No salt is used. If i'm not mistaken (but might be),
> a salt is irrelevant (or unnecessary) in a non-cryptographic
On Tue, Sep 15, 2015 at 1:53 AM, Stephan Beal wrote:
> Indeed, fossil's model allows any hash to be used, but it is not possible
> to change the hash without a near-complete overhaul of fossil (and its
> docs), nor without invalidating every repo in existence, so it's
Following a recommendation to use fossil and Chisel for my very first
open source project, my impression of fossil is very favorable. I've
downloaded fossil to my win7x64 PC, created a repository and am now
trying to set it up as I eventually will on Chisel (I assume).
After starting 'fossil
On Tue, Sep 15, 2015 at 3:54 PM, The Tick wrote:
>
> After starting 'fossil ui', I go Admin->Configuration
>
> The Index page value has the suggestion to use '/home'. I did that. Now,
> how do I create this '/home' page?
>
>From the instructions on that set up page:
The
On 9/14/15, Eric Rubin-Smith wrote:
> See the transcript below for gory details. The summary is:
>
> 1. create a new file on trunk and check it in.
> 2. edit the file and check in on a branch (let's call it "beta")
> 3. trunk decides it wants that particular change set from
> Merge is done by a classic 3-way diff. It looks at all the changes
> that occurred on the path from A to B and applies those same changes
> to C. (A in this case would be the most recent common ancestor of B
> and C).
>
> How would cherry-picks factor into this?
>
Sorry, maybe I'm confused.
Fossil knows nothing about syntax of any sort, so a merge must consider any
change as significant. Try reindenting a python script, where whitespace is
part of the syntax. Diff can be told to ignore changes in spacing, iirc. If
you switch from unix EOL to Windows EOL fossil will see the whole file
On 14 September 2015 at 13:58, Warren Young wrote:
> On Sep 12, 2015, at 9:54 AM, Oliver Friedrich <
> redtalonof+mailingl...@gmail.com> wrote:
> >
> > with nested repositories my administration overhead would exceed even
> the single repository solution, right?
>
> The
29 matches
Mail list logo