Well, it looks like i have to round trip through git anyhow, as a lot
of the repos created by direct bzr fast-export | fossil import come
up empty past the initial commit. Curious and curiouser.
On 10 September 2014 17:47, Richard Hipp d...@sqlite.org wrote:
On Wed, Sep 10, 2014 at 11:38 AM,
On 11 September 2014 01:06, Andy Bradford
amb-sendok-1413003970.hefagogaedafkffga...@bradfords.org wrote:
Thus said David Mason on Thu, 11 Sep 2014 00:42:09 -0400:
: Daves-MacBook-Retina-784 ; cat .fossil-settings/allow-symlinks
yes
: Daves-MacBook-Retina-784 ; fs ci -m test
New_Version:
On Sat, Sep 06, 2014 at 06:05:33PM -0600, Scott Robison wrote:
On Sat, Sep 6, 2014 at 5:24 PM, Nico Williams n...@cryptonector.com wrote:
git branch -D name
Eh, filesystems let you delete files. Unlike most filesystems, git lets
you restore your deleted branches (yes, provided you
On Wed, Sep 10, 2014 at 10:47 PM, Richard Hipp d...@sqlite.org wrote:
On Wed, Sep 10, 2014 at 10:48 PM, Matt Welland estifo...@gmail.com wrote:
On Wed, Sep 10, 2014 at 5:12 PM, Richard Hipp d...@sqlite.org wrote:
Sometimes we will make a check-in to trunk then later decide it doesn't
belong
On Thu, Sep 11, 2014 at 11:50 AM, Nico Williams n...@cryptonector.com
wrote:
On Wed, Sep 10, 2014 at 10:47 PM, Richard Hipp d...@sqlite.org
On the few cases when this has happened to me, I've moved goof into a
new
branch (typically mistake) then cherry pick the follow-on check-ins
back
On Thu, Sep 11, 2014 at 10:18 AM, John Long codeb...@inbox.lv wrote:
On Sat, Sep 06, 2014 at 06:05:33PM -0600, Scott Robison wrote:
On Sat, Sep 6, 2014 at 5:24 PM, Nico Williams n...@cryptonector.com wrote:
git branch -D name
Eh, filesystems let you delete files. Unlike most
On Thu, Sep 11, 2014 at 11:01 AM, Richard Hipp d...@sqlite.org wrote:
On Thu, Sep 11, 2014 at 11:50 AM, Nico Williams n...@cryptonector.com
wrote:
On Wed, Sep 10, 2014 at 10:47 PM, Richard Hipp d...@sqlite.org
On the few cases when this has happened to me, I've moved goof into a
new
On Thu, Sep 11, 2014 at 12:07 PM, Nico Williams n...@cryptonector.com
wrote:
Nothing can really be made immutable, but you can detect mutation.
No. Version 9491ba7d738528f168657adb43a198238abde19e (the SQLite 3.8.6
release) cannot be modified in any way without changing its hash value,
thus
On Thu, Sep 11, 2014 at 11:18 AM, Richard Hipp d...@sqlite.org wrote:
On Thu, Sep 11, 2014 at 12:07 PM, Nico Williams n...@cryptonector.com
wrote:
Nothing can really be made immutable, but you can detect mutation.
No. Version 9491ba7d738528f168657adb43a198238abde19e (the SQLite 3.8.6
On Thu, Sep 11, 2014 at 11:19 AM, Stephan Beal sgb...@googlemail.com wrote:
No, he can't. Well, he can, but he will break the hashes of other records,
so any tamping will be noticed. Specifically, the Z- and R-cards detect any
sort of tampering.
Right. He can. If you've not pushed the
On Thu, Sep 11, 2014 at 6:33 PM, Nico Williams n...@cryptonector.com
wrote:
On Thu, Sep 11, 2014 at 11:19 AM, Stephan Beal sgb...@googlemail.com
wrote:
No, he can't. Well, he can, but he will break the hashes of other
records,
so any tamping will be noticed. Specifically, the Z- and
On Wed, Sep 10, 2014 at 1:23 PM, Stephan Beal sgb...@googlemail.com wrote:
On Wed, Sep 10, 2014 at 7:04 PM, Ron W ronw.m...@gmail.com wrote:
Is it not possible to define an open-ended list of name-value pairs?
Sure we can, but then we've got a data format nobody can predict, which
doesn't
On Thu, Sep 11, 2014 at 7:03 PM, Ron W ronw.m...@gmail.com wrote:
As best I can determine, Fossil already demands that whomever adds custom
fields take responsibility for the customized New Ticket, View Tick and
Edit Ticket pages and associated TH1 apply the semantics correctly and
Thus said David Mason on Thu, 11 Sep 2014 10:14:02 -0400:
committing .fossil-settings/allow-symlinks first doesn't. This looks
like a bug to me... what is the point of version-able allow-symlinks?
Actually, it does work. The problem isn't with the versionable setting.
There is a bug, but
On Thu, Sep 11, 2014 at 12:09 PM, Nico Williams n...@cryptonector.com
wrote:
On Thu, Sep 11, 2014 at 11:01 AM, Richard Hipp d...@sqlite.org wrote:
On Thu, Sep 11, 2014 at 11:50 AM, Nico Williams n...@cryptonector.com
wrote:
On Wed, Sep 10, 2014 at 10:47 PM, Richard Hipp d...@sqlite.org
On Thu, Sep 11, 2014 at 12:18 PM, Richard Hipp d...@sqlite.org wrote:
(Unless you can mount a pre-image attack against SHA1 - let's assume that
is impossible.)
FYI, FWIW, SHA1 seems to be deprecated. There was a summary on slashdot.org
about Google planning to change Chrome's default setting
Hi,
I would expect, having started a server with basename (say)
http://localhost/fossil to be able to proxy URLs of the form 'GET
/fossil/logo ...' and have fossil strip the /fossil prefix (ie: basename)
from the URL, and respond with the logo.
I understand that --basename modifies the links
'Lo.
The fossil build scripts seem to be unable to find openssl on FreeBSD
9.2. It has a choice of the version included with the base system
(in /usr) or the version available from FreeBSD ports (/usr/local),
but it can't seem to find either of them.
Is there any way to get it to give more
On Thu, Sep 11, 2014 at 2:55 PM, Colin McCormack mcc...@gmail.com wrote:
Hi,
I would expect, having started a server with basename (say)
http://localhost/fossil to be able to proxy URLs of the form 'GET
/fossil/logo ...' and have fossil strip the /fossil prefix (ie: basename)
from the URL,
On Thu, Sep 11, 2014 at 1:14 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, Sep 11, 2014 at 7:03 PM, Ron W ronw.m...@gmail.com wrote:
As best I can determine, Fossil already demands that whomever adds custom
fields take responsibility for the customized New Ticket, View Tick and
Edit
org.fossil-scm.fossil-us...@io7m.com wrote:
'Lo.
The fossil build scripts seem to be unable to find openssl on FreeBSD
9.2. It has a choice of the version included with the base system
(in /usr) or the version available from FreeBSD ports (/usr/local),
but it can't seem to find either of
I know that this goes against the philosophy of Fossil, and I realize
that I am entering dirty hack territory. Nevertheless, I am wondering
how I can remove a user that has made no commits, no ticket
updates/additions, and no wiki updates/additions whatsoever. Is it
enough to say:
delete
On 2014-09-11T16:09:42 -0400
Eric Rubin-Smith eas@gmail.com wrote:
I skimmed through the configure code. Looks like you need to have
the subdir and file 'openssl/ssl.h' beneath the dir you specify, and
the subdir and files 'lib/libssl.so' and 'lib/libcrypto.so' beneath the
dir you
On Thu, Sep 11, 2014 at 4:21 PM, Philip Bennefall phi...@blastbay.com
wrote:
I know that this goes against the philosophy of Fossil, and I realize that
I am entering dirty hack territory. Nevertheless, I am wondering how I
can remove a user that has made no commits, no ticket
On 11 September 2014 13:50, Andy Bradford
amb-sendok-1413049836.aenikllhaaeaihnhp...@bradfords.org wrote:
Actually, it does work. The problem isn't with the versionable setting.
There is a bug, but its in fossil open, not the setting.
After you open the fossil, delete the link (which is
(sorry for the funky formatting, Mailman)
I wrote:
I would expect, having started a server with basename (say)
http://localhost/fossil to be able to proxy URLs of the form 'GET
/fossil/logo ...' and have fossil strip the /fossil prefix (ie: basename)
from the URL, and respond with the logo.
I see this is essentially a duplicate of this bug:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg11051.html
which was reported about 18 months ago, with a patch.
On Thu, Sep 11, 2014 at 3:18 PM, Colin McCormack mcc...@gmail.com wrote:
(sorry for the funky formatting,
On 12 Sep 2014, at 5:06 am, org.fossil-scm.fossil-us...@io7m.com wrote:
'Lo.
The fossil build scripts seem to be unable to find openssl on FreeBSD
9.2. It has a choice of the version included with the base system
(in /usr) or the version available from FreeBSD ports (/usr/local),
but it
28 matches
Mail list logo
