Thus said Richard Hipp on Sun, 21 Jan 2018 18:49:51 -0500:
> Andy's original problem was two separate bugs. This is yet a third.
> They should all be fixed now, by separate check-ins.
I can confirm that the 2 I mentioned are fixed.
Thanks,
Andy
--
TAI64 timestamp: 40005a655367
_
Thus said Stephan Beal on Sun, 21 Jan 2018 23:03:44 +0100:
> Anyone notice that the Comment and Original Comment are identical in
> the Overview section, but that the yellow highlighted entry shows a
> modified comment? That doesn't seem right.
I hadn't noticed, however, perhaps the timelin
Thus said "Andy Bradford" on 20 Jan 2018 21:05:25 -0700:
> http://www.fossil-scm.org/index.html/info/41f35ca4ec617891
It looks like this commit also broke the command line. It used to be
possible to use ``fossil annotate'' from a relative path in the wo
Hello,
The bug is that if you run ``fossil ui'' from within a subdirectory of a
working checkout, then try to annotate source files fossil crashes with
SIGSEGV and dumps core.
I haven't had the time to fix this so I'm reporting it now in the event
that I don't get around to fixing it. As far a
Thus said Richard Hipp on Mon, 15 Jan 2018 11:27:20 -0500:
> I will accept check-ins to a branch that invoke the fossil_pledge(X,Y)
> utility function.
I've added a new branch called pledge-additions with additional pledge()
restrictions for the status command. We can continue to pledgify other
Thus said Richard Hipp on Mon, 15 Jan 2018 11:27:20 -0500:
> I will accept check-ins to a branch that invoke the fossil_pledge(X,Y)
> utility function. The fossil_pledge(X,Y) function is a macro that
> evaluates to a no-op except when compiled with -DFOSSIL_HAVE_PLEDGE.
> If the FOSSIL_HAVE
Thus said Warren Young on Wed, 11 Oct 2017 14:09:02 -0600:
> My change on line 70 of Makefile is a GNU make conditional. I'm
> guessing you're using BSD make or some other non-GNU make, which
> doesn't grok that syntax.
Yes, it is BSD make (on OpenBSD).
BSD make does have condition
Thus said Warren Young on Tue, 10 Oct 2017 19:38:52 -0600:
>http://fossil-scm.org/index.html/timeline?r=wy-autoreconfig
I see that this change has been merged, however, now it has problems on
trunk which I don't have time to delve into at the moment. I'll look at
it later if it doesn't get
Thus said "Andy Bradford" on 26 Sep 2017 14:11:59 -0600:
> Am I missing something?
It looks like ``fossil bisect'' identifies this commit as having
introduced changed behavior:
http://www.fossil-scm.org/index.html/info/d9ef474a1a319217
However, I noticed
Hello,
I'm seeing some strange behavior with this fossil version:
This is fossil version 2.4 [398a90c006] 2017-09-26 14:47:20 UTC
Specifically, I'm trying to annotate db.c in the Fossil respository:
http://www.fossil-scm.org/index.html/annotate?filename=src/db.c&checkin=ce1bc4fb09fbeed6
Line 2
Thus said Richard Hipp on Fri, 11 Aug 2017 11:41:09 -0400:
> I don't feel a particular need to rush out a new release containing
> this fix. But I am open to arguments to the contrary, if you feel
> differently.
I think at a certain point, users of any software have to take their
own
Thus said Richard Hipp on Mon, 12 Jun 2017 05:02:15 +0200:
> Do you still have that pair of files, and can you share them?
I might still have them. I'll see if I can find them and report back.
Regarding the extraordinarily long lines, I'm not sure what is
considered extraordinary, bu
Thus said Richard Hipp on Sun, 11 Jun 2017 22:58:00 +0200:
> I added an experimental option to Fossil's diff-er, the --yy option,
> that runs slower but does a better job. It still need improvement
> though. You can compare as follows:
I had a similar problem where I needed an accurate si
Thus said Stephan Beal on Sat, 03 Jun 2017 05:02:57 +0200:
> My continued respect and appreciation go out to all of you who have
> helped me, in one way or another, to work on software over the years.
> To you i wish Happy Hacking!
You're code contributions will be missed.
Thank you for your
Hello,
While looking at a recent bug reported on the fossil-users list, I
realized that file_simplify_name() has a problem:
http://www.fossil-scm.org/index.html/artifact?ln=802+841&name=c77e7c7383f414c6
Specifically, it doesn't check that z is not NULL. This later results in
a segfault (li
Thus said Ross Berteig on Fri, 14 Apr 2017 16:09:18 -0700:
> I'm also considering an extension to the glob_create() function to add
> support for comments in lists of GLOBs.
If I have a program that generates files that begin with # that I want
to ignore, would this be accomplished if suppo
Thus said Richard Hipp on Tue, 04 Apr 2017 09:33:40 -0400:
> I'm inclined to ignore their offer, as adding fossil-scm.com is
> just one more DNS entry to maintain. But I am open to acquiring
> fossil-scm.com (and pointing it to exactly the same webserver as
> fossil-scm.org) if
Thus said Richard Hipp on Wed, 01 Mar 2017 17:35:56 -0500:
> All other SHA1 hashes remain the same. If you doubt that assertion,
> you can test it by running "fossil test-integrity" or "fossil all
> test-integrity".
On a side note, it appears that test-integrity is slightly slower than
Thus said Roy Keene on Tue, 28 Feb 2017 11:13:01 -0600:
>e. If a collision is submitted (e.g., same SHA1, different SHA256)
>the artifact (by SHA1) is considered compromised and shunned from
>the repository (or something)
Why would this constitute a collision? Wouldn't a collision
Thus said Richard Hipp on Mon, 27 Feb 2017 21:50:43 -0500:
> (9) There are no changes to the file formats, other than relaxing the
> size constraint on artifact hashes - allowing hash to be greater than
> or equal to 40 characters rather than requiring it to be exactly 40
> characters.
The F
Thus said Kevin Martin on Mon, 13 Feb 2017 07:57:46 +:
> I am guessing I am not building it right? But I do know the file is
> being recompiled because if I introduce an error in the file it fails
> to build.
Try running ``make clean'' and then build again?
Andy
--
TAI64 timestamp: 4000
Hello,
While looking at the code to understand a recently added feature, I
found what appears to be a bug:
http://www.fossil-scm.org/index.html/artifact?name=25ce5d1f89690ab3&ln=921
I highly doubt that $ was intended to be looked for twice; if not what
was the intended 3rd character suppo
Thus said Richard Hipp on Mon, 02 Jan 2017 14:14:59 -0500:
> SQLite version 3.16.0 is now checked into Fossil. Perhaps this would
> be a good time to do another release of Fossil.
I think so. It would be good to run through some tests first as there
are some important bug fixes that came int
Thus said Zakero on Thu, 22 Dec 2016 16:07:52 +0400:
> A few weeks ago, Andy asked me to try to reproduce
> this problem with older versions of fossil. The check-in
> "41c2220934de8cb8d90126d5083df3e95e961b8c" is where the problem first
> appears. This also mirro
Thus said Zakero on Sun, 16 Oct 2016 18:45:41 -0500:
> Ran into an interesting problem yesterday when merging branches:
>
> SQLITE_CONSTRAINT: abort at 41 in [INSERT INTO
> vfile(vid,chnged,deleted,rid,mrid,isexe,islink,pathname) SELECT
> 21178,3,0,rid,mrid,isexe,islink,pathname FROM vfile WHERE
Thus said Richard Hipp on Tue, 18 Oct 2016 15:48:57 -0400:
> it is reported that Hg has developed a blame-cache mechanism that
> makes "blame" and "annotate" about 10x faster. If anybody wants to
> look into this and see if something similar could be done for Fossil,
> that would be grea
Thus said "Andy Bradford" on 27 Oct 2016 21:42:34 -0600:
> I always run ``make distclean'' not ``make distclean'' but since you
> suggest it, here's the difference on my system:
Minor correction, I always run ``make clean'' not ``make distc
Thus said "Joe Mistachkin" on Thu, 27 Oct 2016 17:22:26 -0700:
> I was unable to reproduce the stated linker error even without this
> change. Given that the generated header files all seem to wrap
> references to "fusefs_cmd" in #if blocks, I'm not sure how it's
> possible unles
Thus said Baruch Burstein on Thu, 27 Oct 2016 18:01:54 +0300:
> Please review https://www.fossil-scm.org/index.html/info/8ae790623c14ac5c.
Very nice fix!
Thanks,
Andy
--
TAI64 timestamp: 400058125848
___
fossil-dev mailing list
fossil-dev@maili
Thus said Baruch Burstein on Thu, 27 Oct 2016 16:05:01 +0300:
> I am having trouble figuring out how to get the exact number
Either of these will show that information:
fossil info
fossil dbstat
Andy
--
TAI64 timestamp: 4000581207df
___
fossil-
Thus said Stephan Beal on Tue, 18 Oct 2016 08:00:05 +0200:
> Fyi, the "too many bounces" problem is now apparently hitting gmail
> users.
What would be really helpful is a copy of one of the bounces that was
received by the MLM.
Andy
--
TAI64 timestamp: 40005805c0ef
Thus said Zakero on Sun, 16 Oct 2016 18:45:41 -0500:
> SQLITE_CONSTRAINT: abort at 41 in [INSERT INTO
> vfile(vid,chnged,deleted,rid,mrid,isexe,islink,pathname) SELECT
> 21178,3,0,rid,mrid,isexe,islink,pathname FROM vfile WHERE id=4735]: UNIQUE
> constraint failed: vfile.pathname, vfile.
> fossil
Thus said "Joe Mistachkin" on Sat, 15 Oct 2016 17:46:54 -0700:
> stash-fixes
I've gone ahead and merged this. Thanks for updating the test case.
Andy
--
TAI64 timestamp: 40005802d678
___
fossil-dev mailing list
fossil-dev@mailinglists.sqli
Thus said Ross Berteig on Fri, 14 Oct 2016 12:14:03 -0700:
> Something made the Windows Firewall fussier, and I had to reassure it
> during both test suite runs that yes, it was ok to let fossil.exe do
> something. The prompt came a long ways in to the suite, but I didn't
> check the prot fil
Thus said "Andy Bradford" on 14 Oct 2016 10:14:20 -0600:
> I'm not sure what the unversioned failures are at this point.
The unversioned test failures were caused by the fact that I already had
a fossil server running on port 8080. This obviously didn't work out
b
Thus said Richard Hipp on Fri, 14 Oct 2016 10:47:24 -0400:
> The final SQLite 3.15.0 is not checked into the Fossil trunk. Is it an
> appropriate time to release version 1.36 of Fossil?
I get the following test results on OpenBSD 5.8:
* Final results: 14 errors out of 34413 tests
* Consi
Hello,
Currently, ``fossil timeline'' will return an empty set when providing
options that don't really make sense:
$ fossil timeline src/timeline.c
+++ no more data (0) +++
I believe an error here would be more appropriate:
$ ./fossil timeline src/timeline.c
unknown check-in or invalid date:
Hello,
I recently had the need to view a diff of a specific check-in from the
command line and found that while using --to and --from can accomplish
it, it's a bit tedious.
Please provide feedback on the changes now introduced in the
diff-show-changes branch:
http://www.fossil-sc
Thus said Ross Berteig on Mon, 26 Sep 2016 13:56:22 -0700:
> The branch may have been good before the merge from trunk, but it is a
> mess right now. It needs cleanup and likely merging from something
> closer to the tip of trunk.
Indeed, at the time I sent the email, it worked. It l
Thus said "Joe Mistachkin" on Thu, 22 Sep 2016 19:32:13 -0700:
> stash-fixes -- FIX: Seems relatively straightforward?
I think this one is pretty much ready, but if someone wants to take a
look to make sure the SQL is right, that might be good. I believe it
passes all the test cases.
Thus said "Joe Mistachkin" on Tue, 20 Sep 2016 09:44:08 -0700:
> Please review the changes on the "autosetupAndJimTcl" branch, which
> updates the included autosetup and Jim with the latest code from
> upstream.
I took a look at the changes, which were many, and noticed a lot more
use
Thus said Stephan Beal on Fri, 18 Mar 2016 15:53:38 +0100:
> i actually like the www2 one better, as it clearly shows that two
> branches (green/teal) are still opened but have not been edited
> "recently".
I think I still prefer the old style as well, but I'm not sure if that
is ju
Thus said "Joe Mistachkin" on Thu, 10 Mar 2016 19:52:08 -0800:
> I've briefly looked over the changes; however, it would be good if
> others could review and/or provide feedback on them as well.
After some discussion with Ross, I think there may be some improvements
that could be made in th
Thus said Ross Berteig on Wed, 02 Mar 2016 19:24:55 -0800:
> Yes, apparently it has. In isValidLocalDb() in src/db.c ca. line 1099,
> there are two if blocks that test for some feature of the local db
> schema, and to the needed ALTER TABLE commands to fix things up.
The ALTER TABLE commands
Thus said Ross Berteig on Wed, 02 Mar 2016 15:20:52 -0800:
> One of the changes was to the schema of the table used by the stash in
> the local (per checkout) database, which was going to require that
> every open checkout be re-opened.
This is only if they want to be able to stash a rename i
Hello,
Are there any other issues that could be addressed in the stash-fixes
branch? If not, I would like to merge it. Basically it cleans up the
ability to stash a rename.
Thanks,
Andy
--
TAI64 timestamp: 400056d70a74
___
fossil-dev mail
Thus said Stephan Beal on Sat, 20 Feb 2016 14:24:31 +0100:
> My proposal is that we standardize on the /foo/x form for all
> generated links. Justification: they simply look better :/.
I don't see a problem with this, and as long as old generated links
which include ?name= still w
Thus said Stephan Beal on Sat, 06 Feb 2016 20:12:04 +0100:
> But this did the trick:
>
> tclsh $PWD/../fossil/test/tester.tcl $PWD/../fossil/fossil
And now you shouldn't even need that trick:
http://www.fossil-scm.org/index.html/info/25f7d3c1030fa4aa
By the way, I no longer seem to be able
Thus said Stephan Beal on Sat, 06 Feb 2016 20:12:04 +0100:
> > couldn't open "../fossil-src/test/fossil_prompt_answer": no such
> > file or directory
> >
>
> where did 'fossil-src' come from?
That's just the name of my test repository for running tests.
In your case it was just ../fossil, bu
Thus said Stephan Beal on Sat, 06 Feb 2016 18:46:04 +0100:
> [stephan@host:~/cvs/fossil/ftest]$ tclsh ../fossil/test/tester.tcl
> ../fossil/fossil
That's the ticket! Apparently calling it with a relative path doesn't
work very well and I now see:
...
couldn't open "../fossil-src/test/fossil_
Thus said Stephan Beal on Sat, 06 Feb 2016 18:25:03 +0100:
> [stephan@host:~/cvs/fossil/ftest]$ tclsh --version
> % [stephan@host:~/cvs/fossil/ftest]$ tclsh -?
> % [stephan@host:~/cvs/fossil/ftest]$ tclsh --help
> % [stephan@host:~/cvs/fossil/ftest]$
>
> i give up...
I don't think it's actually r
Thus said "Andy Bradford" on 06 Feb 2016 10:06:58 -0700:
> > couldn't open "../fossil/test/fossil_prompt_answer": no such file or
> > directory while executing
>
> Seems that something changed the behavior of how fossil_prompt_answer
> is found.
Thus said Stephan Beal on Sat, 06 Feb 2016 14:38:05 +0100:
> couldn't open "../fossil/test/fossil_prompt_answer": no such file or
> directory
> while executing
By the way, I'm unable to reproduce this error. It works fine with:
$ /tmp/fossil-src/fossil ver
This is fossil version 1.35 [626276
Thus said Stephan Beal on Sat, 06 Feb 2016 14:38:05 +0100:
> couldn't open "../fossil/test/fossil_prompt_answer": no such file or
> directory
> while executing
Seems that something changed the behavior of how fossil_prompt_answer is
found. fossil_prompt_answer is a Tcl proc, but this error w
Thus said Ross Berteig on Sat, 23 Jan 2016 16:48:45 -0800:
> I should add that it is not unique to my new file json.test. I've seen
> it happen other calls to repo_init when all tests are run. Since it is
> treated as an exception by Tcl, the tests halt at that point.
I have not seen this at all
Thus said Richard Hipp on Fri, 15 Jan 2016 07:46:17 -0500:
> I received email alerting me to the following:
> https://www.xssposed.org/incidents/124372/
There are free tools that could be run to check their claims...
These folks might have one:
https://www.owasp.org/index.php/Cross-site_Scripti
Thus said Ross Berteig on Wed, 13 Jan 2016 12:47:56 -0800:
> Even if we do this, which in daylight still seems like a good idea for
> portability, amend.test probably ought to defend against a global
> setting for "editor".
For now, instead of relying on environment variables which have l
Thus said Ross Berteig on Tue, 12 Jan 2016 15:53:08 -0800:
> * amend-comment-5.1
> * amend-comment-5.2
> * amend-comment-5.3
> * amend-comment-5.4
These are due to "ed" missing in your environment. Is there a
similar tool that exists for Windows that could be used to autom
Thus said Richard Hipp on Fri, 08 Jan 2016 06:00:43 -0500:
> There is no logic for "merge" to detect no-op merges and refuse to
> record them. But I suppose we could add that.
Would that affect this kind of merge?
http://core.tcl.tk/tcl/info/1b40769a10057805
Thanks,
Andy
--
TAI64 timestam
Thus said Ross Berteig on Thu, 07 Jan 2016 23:55:12 -0800:
> Exactly. And I think it is a good idea for the test suite to run from
> a folder outside of all checkouts for a lot of reasons.
Perhaps we should update the test: make target to create a temporary
directory, cd to it and run tests
Thus said Ross Berteig on Thu, 07 Jan 2016 11:54:03 -0800:
> Letting the full test suite run in-tree fails almost immediately
> because amend.test called repo_init which cannot be run inside a
> checkout.
Any tests that require their own repository will fail if you run it from
within
Thus said Ross Berteig on Wed, 06 Jan 2016 12:37:28 -0800:
> Because of that comment and Richard's advice to test out of tree to
> avoid that issue, I haven't run a test in tree. I suppose I should
> pull a fresh clone and try it to better understand the issue.
What I do is in my main chec
Hello,
Due to recent discussions about possible sync failures I started looking
at the cluster code again and noticed that Fossil does not crosslink in
clusters. I noticed that it causes at least these 2 problems:
1) fossil test-clusters returns that all artifacts are unreachable,
because t
Hello,
This recent commit broke autosync pull-only/pullonly settings:
http://www.fossil-scm.org/index.html/info/5853fcf132800f90
I went ahead and restored the historical behavior here:
http://www.fossil-scm.org/index.html/info/acc0200a4ab9b4c5
Thanks,
Andy
--
TAI64 timestamp: 40005651539
Thus said "Joe Mistachkin" on Sat, 21 Nov 2015 10:38:46 -0800:
> Apparently, a fix was done on a branch, but never made it to trunk?
That would explain why I didn't see the previous fix. I actually did
look through annotations to see how it slipped by since 2008, but didn't
notice that it was
Hello,
I ran into a segfault:
(gdb) bt
#0 0x1a710bd7 in proc_command (interp=0x83592c20, ctx=0x0, argc=4,
argv=0x802ba400, argl=0x802ba410) at ./src/th_lang.c:500
#1 0x1a70f295 in thEvalLocal (interp=0x83592c20, zProgram=Variable "zProgram"
is not available.
) at ./src/th.c:917
#2 0x1a70
Thus said Baruch Burstein on Wed, 26 Aug 2015 11:33:09 +0300:
> When I try to clone the fossil repo from https://fossil-scm.org, I get
> an error that the SSL certificate is for sqlite.org. I also get this
> error when browsing to https://fossil-scm.org. Is this a configuration
> error?
I get n
Thus said "K. Fossil user" on Mon, 17 Aug 2015 22:21:09 -:
> 2) ... When I do reply then it is the guy mail that is in my "to"
> field which may bother some people. Someone was a bit angry when I do
> respond to his personal email : I wasn't aware about the issue. I am
> NOT bothered
Hello,
I sent this out earlier, but it seems to have been lost (perhaps spam
filters didn't like something in it; maybe they won't like this one
either).
Basically, I encountered a segfault because I incorrectly passed in a
NULL pointer to blob_append. I thought that blob_append shou
Thus said "Andy Bradford" on 01 Aug 2015 23:17:52 -0600:
> Specifically, where I ran into it, was with:
Sorry, I meant:
http://www.fossil-scm.org/index.html/artifact/c56f142d0d8ec1514d3b586cf3fdf628a9d50523?txt=1&ln=2745
If this ends up being NULL it causes a segfault.
Or sho
Hello,
Just a quick note regarding this commit:
http://www.fossil-scm.org/index.html/info/2d714a4e48251549
I ran into a segfault while testing some of the amend command changes.
Specifically, where I ran into it, was with:
http://www.fossil-scm.org/index.html/artifact/212114657df8d3ccf84ec056
Thus said "Joe Mistachkin" on Wed, 29 Jul 2015 20:01:33 -0700:
> Another good (and recent) example test file is "mv-rm.test", which
> shows how to setup and start munging a dedicated test repository
> during the tests.
Thanks, I'll have a look at that.
I guess these tests are failing
Hello,
To be able to add tests for the new command I've been familiarizing
myself with tester.tcl and the tests. The instructions for using it say:
From a private directory (not the source tree) run "tclsh
$SRC/test/tester.tcl $FOSSIL" where $FOSSIL is the name of the
ex
Thus said Richard Hipp on Mon, 13 Jul 2015 15:34:28 -0400:
> Let's hope it was the "make clean" and not the "fossil rebuild" that
> cleared the problem
It's very likely the make clean.
However, last week I had been rebuilding while tracking down a different
problem which required crossin
Thus said "Andy Bradford" on 13 Jul 2015 13:10:41 -0600:
> $ fossil ver
> This is fossil version 1.33 [501f35e50a] 2015-07-11 23:13:28 UTC
Well, after make clean and a rebuild, I cannot seem to reproduce it
again.
Never mind.
Andy
--
TAI64 timestamp:
Hello,
Today, I fired up ``fossil server'' in my clone of the Fossil
repository, opened a browser and clicked on a link to generate a vdiff,
specifically:
http://localhost:8080/vdiff?from=b9447b0ec60ab6050fca75d767757654c3cf2613&to=2821e284c5337529e8c9f07b26d18f18f676ffcb&sbs=1
The b
Hello,
It looks like [0fc8b9df0c4e27b6] introduced a link-time problem; after
running make clean and then trying to build, I get this error:
...
iwyg.o bld/xfer.o bld/xfersetup.o bld/zip.o bld/sqlite3.obld/linenoise.o
bld/shell.o bld/th.o bld/th_lang.o bld/th_tcl.o bld/cson_amalgam
Thus said Andy Goth on Wed, 20 May 2015 18:30:24 -0500:
> Which browser? In my experience (mostly Firefox), starting the
> selection above the text captures all the way from the start of the
> line. Selecting from below gets the end of the line.
Yes, it's Firefox, and I can select just
Thus said Andy Goth on Wed, 20 May 2015 12:45:12 -0500:
> In typical browsers, it's not possible to start a selection in the
> middle of hyperlink text. Attempting to do so is instead interpreted
> as a drag-and-drop operation.
That's not entirely true, it's just difficult. Especially
Thus said Andy Goth on Wed, 20 May 2015 12:45:12 -0500:
> In typical browsers, it's not possible to start a selection in the
> middle of hyperlink text. Attempting to do so is instead interpreted
> as a drag-and-drop operation.
[Resending becausethe previous message gotheld
Hello,
While testing color popagation on branches due to recent discussion on
the Fossil Users mailing list, I discovered something that apperas to be
a bug. See the branch here.
http://fossil.bradfords.org:8080/timeline
The color of the branch was initially chosen by Fossil with checkin
Thus said Richard Hipp on Tue, 05 May 2015 12:16:46 -0400:
> I've got to work on some other things (getting the SQLite 3.8.10
> release out). Could y'all please check the following links and let me
> know if you see any surplus or missing "added by merge" files?
What does that involve?
Thus said Richard Hipp on Tue, 28 Apr 2015 13:00:13 -0400:
> Why does "fossil clean --emptydirs" prompt for confirmation before
> removing an *empty* directory?
If the directory is exempted in the empty-dirs setting, should it just
ignore the empty directory?
Seems if --emptydirs is set a
Thus said Scott Robison on Thu, 19 Mar 2015 14:26:47 -0600:
> The additional problem with color vision deficiency is that even if we
> found a set of colors that I could always differentiate and always
> rely on, who knows if other color deficient people would see it the
> same way I do.
H
Thus said James Moger on Thu, 19 Mar 2015 08:09:50 -0400:
> It surprises me that IceWeasel has trouble with border-radius. Being
> Debian can I assume it is an older IceWeasel?
Yes, it's a bit older---so take it with a grain of salt, but, I was
pleasantly surprised that I saw no circles (
Thus said Richard Hipp on Wed, 18 Mar 2015 13:41:31 -0400:
> (The SERVERCODE is an historical artifact that is no longer used for
> anything and can be safely ignored.)
I did not realize that it was no longer used; does sync.wiki need an
update? Currently it says:
The servercode argume
Thus said Stephan Beal on Thu, 19 Mar 2015 01:20:01 +0100:
> Not true - branch point leaves have lines going out.
Oh yes, I too had forgotten about those.
By the way, welcome back. :-)
Andy
--
TAI64 timestamp: 4000550a19e7
___
fossil-dev mailin
Thus said Stephan Beal on Wed, 18 Mar 2015 23:13:56 +0100:
> How about one for leaves and the other for non-leaves?
Isn't a leaf easily identified by the fact that it has no descendents
(as indicated by no edges leaving the node)?
Andy
--
TAI64 timestamp: 4000550a06c1
Thus said Richard Hipp on Wed, 18 Mar 2015 16:56:24 -0400:
> Maybe circles should be used in all cases? Or maybe the use of circles
> versus squares should be a skin-selectable option?
I prefer boxes over circles, so definitely if there is a strong desire
to use circles instead of boxes, then
Thus said Jan Danielsson on Wed, 18 Mar 2015 19:21:02 +0100:
> No problems rendering on this system; it Just Works(tm).
It doesn't render on my Debian system which uses Iceweasel (same code
base for Firefox, with policy infringing things removed I believe).
Andy
--
TAI64 timestamp: 400055
Thus said Scott Robison on Wed, 18 Mar 2015 12:03:49 -0600:
> Or hearts & spades & clubs. Maybe pacman & qbert.
Or maybe, hopefully, this can be controlled via CSS...
Andy
--
TAI64 timestamp: 40005509d65b
___
fossil-dev mailing list
fossil-dev@mail
Thus said Richard Hipp on Wed, 18 Mar 2015 13:53:14 -0400:
> https://www.fossil-scm.org/fossil/timeline?y=ci
I've found that in some browsers, all nodes look like squares, not sure
why.
That being said, I prefer a blocky thing with edges to a no-corners
thing when line oriented data is
Thus said Stephan Beal on Sun, 08 Mar 2015 10:55:52 +0100:
> http://www.mail-archive.com/fossil-dev@lists.fossil-scm.org/maillist.html
mail-archive.com uses the mailing list address for uniquely identifying
the list. This changed from fossil-...@lists.fossil-scm.org to
fossil-dev@maili
Thus said Stephan Beal on Wed, 04 Mar 2015 18:35:56 +0100:
> For every "round-trip" the credentials of the remote repository are
> checked. If no key exchange has been done, the password has to be
> entered over and over again.
What version of Fossil are they using? Starting with Fos
Hello,
I just committed some changes that will allow multiple blocks to be
highlighted when using ln= as a query parameter:
http://www.fossil-scm.org/index.html/timeline?r=multi-block-highlight&nd&c=2015-03-06+07%3A39%3A09&n=200
Will someone review the changes and provide feedback? Make
Thus said Richard Hipp on Sat, 21 Feb 2015 13:07:46 -0500:
> Yes. We moved the mailing list server to a different IP address
> (because it wants to use Apache and we are running a different web
> server on port 80 of the machine that was hosting the mailing list.)
> This involved givi
Thus said Vikrant Chaudhary on Thu, 26 Feb 2015 10:21:33 +0530:
> I do wonder though if it could display time in local time-zone instead
> of UTC.
There is a setting in your Fossil repository for that. You can disable
the display of UTC in Admin->Timeline.
Andy
--
TAI64 timestamp: 400054e
Thus said Richard Hipp on Wed, 25 Feb 2015 10:04:54 -0500:
> The dates on timelines (the -MM-DD) could be seen as being in the
> wrong place. The dates are positioned at a point on the timeline where
> the HH:MM:SS for the date is 23:59:59.999. But since the HH:MM:SS is
> not shown, that im
Thus said Richard Hipp on Sat, 21 Feb 2015 13:07:46 -0500:
> The change has fixed a lot of problems that we were previously having
> due to running Apache on port 8080. I'm sorry to hear that it caused
> some confusion for you.
Don't worry about it. I just wanted to confirm that the chan
Hello,
Has there been a mailing list change? I notice that the List-id
has changed and is no longer fossil-dev.lists.fossil-scm.org. I
used to filter on the List-post header which has always been
fossil-...@lists.fossil-scm.org but appears to have changed recently to
1 - 100 of 102 matches
Mail list logo
