Ping.
On Thu, 21 Jun 2018 22:18:37 +1000
wrote:
> It appears the "show-version-diffs" setting was abandoned in commit
> 0a1f4ed6aa.
>
> Index: src/setup.c
> ==
> --- src/setup.c
> +++ src/setup.c
> @@ -1463,19 +1463,10 @@
>@ i
It appears the "show-version-diffs" setting was abandoned in commit 0a1f4ed6aa.
Index: src/setup.c
==
--- src/setup.c
+++ src/setup.c
@@ -1463,19 +1463,10 @@
@ in a separate box (using CSS class "timelineDate") whenever the date
c
That makes sense, but what I'm saying is, why bother with the
compile-time flag?
It seems desirabe to allow the user to configure this behavior with
repository settings, rather than using a flag to determine if it is
hard-coded or not.
Are there a lot of legacy scripts out there that are difficul
Hello,
I am trying to understand the idea behind FOSSIL_ENABLE_LEGACY_MV_RM.
It has been around for a while, and it is the only compile-time flag that
determines if a setting is hard-coded or if it is obtained from the repository
config.
It appears that if this is not defined, the "mv" and "rm"
On Mon, 4 Jun 2018 03:43:19 +0200
Stephan Beal wrote:
> On Mon, Jun 4, 2018, 03:33 Richard Hipp wrote:
>
> > On 6/3/18, Richard Hipp wrote:
> > >
> > > So, if anybody sees any last minute tidying up that we need to do...
> >
> > For example, on the front page
> > (https://fossil-scm.org/in
- Paleo
- Jurassic
- Diatom
- Trilobyte
Better yet, find a term begining with 'C' so that you can have the
'C Versioning System.'
On Wed, 6 Jun 2018 21:26:22 -0400
Eduard wrote:
> I might enable public registration 'soon'. Now all I need is a catchy
> name, like `chiselapp` :p
I think Peter is referring to deleting users from the "user" table.
Fossil keeps the commit history forever, and each manifest has the name
of the user that made the commit. In the database, this is recorded in
the user column of the "event" table as the name of the user that made
the commit.
The
Given over half of a typical repository is a delta, this is not a bad
idea. It will allow you to optimize some of the SQL for delta lookups.
On Mon, 22 Jan 2018 21:04:26 -0500
Richard Hipp wrote:
> On 1/22/18, bytevolc...@safe-mail.net wrote:
> > In rebuild.c (commit 1a95af721e467a6e3321c1557c4
In rebuild.c (commit 1a95af721e467a6e3321c1557c4f0cdfa353ef4a):
Ln 168:
db_multi_exec(
"CREATE VIEW IF NOT EXISTS "
" repository.artifact(rid,rcvid,size,atype,srcid,hash,content) AS "
"SELECT blob.rid,rcvid,size,1,srcid,uuid,content"
" FROM blob LEFT JOIN delta ON (blo
What's up with this comment in add.c starting at line 27:
/*
** WARNING: For Fossil version 1.x this value was always zero. For Fossil
** 2.x, it will probably always be one. When this value is zero,
** files in the checkout will not be moved by the "mv" command and
**
Looks like this resolves the issue.
On Thu, 30 Nov 2017 13:10:09 -0500
Richard Hipp wrote:
> Can you rebuild using the latest check-in on the symlink-refactor
> branch (https://www.fossil-scm.org/fossil/info/b2594738460036b9) and
> let me know whether or not this problem is resolved?
On Thu, 30 Nov 2017 13:19:38 +0100
Jan Nijtmans wrote:
> This patch has no relation to fossil's symlink support, it's just part
> of the code to find a suitable temporary directory to write some
> intermediate file. It's unfortunate it's that complicated, but useful
> because sometimes the workin
On Mon, 27 Nov 2017 13:58:14 -0700
Warren Young wrote:
> On Nov 23, 2017, at 5:19 AM, bytevolc...@safe-mail.net wrote:
> >
> > They want maximum results for minimum effort? That may be normal, but
> > it's still whiney.
>
> If “normal” is “whiney”, it ceases to be a useful disparagement unles
On Mon, 27 Nov 2017 09:52:19 -0500
Richard Hipp wrote:
> I am in receipt of your patch. I have not evaluated it yet because
> the entire symbolic-link mechanism in Fossil is confused and very
> difficult to manage. It mostly works now, but is brittle. A
> seemingly simple patch like what you s
Ping.
On Sat, 25 Nov 2017 11:42:29 +
bytevolc...@safe-mail.net wrote:
Index: src/file.c
==
--- src/file.c
+++ src/file.c
@@ -327,24 +327,30 @@
** zFilename is a directory -OR- a symlink that points to a directory.
** Return 0 if
On Sat, 25 Nov 2017 18:46:52 -0600
Zakero wrote:
> To help make the ellipses more visible, you could put them in their
> own and let the skin figure out what looks best. Also,
> instead of using "...", what about "[+]"?
If it's going at the end of the text, how about ">>>"?
__
Fixed a typo resulting in absolute cases not being picked up well.
Index: src/file.c
==
--- src/file.c
+++ src/file.c
@@ -327,24 +327,30 @@
** zFilename is a directory -OR- a symlink that points to a directory.
** Return 0 if zFilen
Fixed patch, an '{' had escaped the other patch somehow.
Index: src/file.c
==
--- src/file.c
+++ src/file.c
@@ -327,24 +327,30 @@
** zFilename is a directory -OR- a symlink that points to a directory.
** Return 0 if zFilename does n
On OpenBSD 6.1, running "fossil uv edit" will result in the
following error:
unable to create directory /var/tmp
Upon digging through this, I found Fossil was following the "/var/tmp"
symlink that recent OpenBSD versions create:
lrwxrwx--- 1 root wheel 6 Apr 1 2017 /var/tmp -> ../tmp
Of
On Wed, 22 Nov 2017 21:35:31 -0700
Warren Young wrote:
> The Fossil vs Git UI situation has been studied before. There’s a
> tremendous amount of logical mismatch between the two, such that
> commands for one often cannot be translated 1:1 to the other.
>
> Just as a single example:
>
> $
I noticed this curious gem in the test_env web page, which doesn't have
any obvious use case, and I cannot find any mentions of
"test_env?redirect=..." anywhere in the Fossil code base.
Index: src/style.c
==
--- src/style.c
+++ src/st
On Wed, 22 Nov 2017 23:43:07 +
Javier Guerra Giraldez wrote:
> i _have_ used fossil running in a very small MIPS system. as
> mentioned, it's really nice to pull versioned stuff like
> configurations, HTML, binary blobs. yes, i used gcc to compile it,
> but what was small two years ago now
On Wed, 22 Nov 2017 17:30:10 +
Javier Guerra Giraldez wrote:
> why not? fossil makes for a neat deployment client! yes, it can also
> be done with just an http client, but still is a nice option to have.
Because people do not use compilers on such systems, but rather, they
use other systems
On Tue, 21 Nov 2017 16:42:56 -0700
Warren Young wrote:
> > This seems more like a complaint about the user interface.
>
> How does that observation get us to a different solution?
Because you then focus on tweaking the UI to make it better, rather
than just stuffing support for other VCSes be
On Mon, 20 Nov 2017 17:44:49 -0700
Warren Young wrote:
> On Nov 20, 2017, at 4:57 PM, bytevolc...@safe-mail.net wrote:
> >
> > Why add more complexity and bloat to the Fossil core?
>
> Because interoperability. One of the major arguments against using
> Fossil is that it’s largely a one-way
In setup_ulist web page, the "Last Change" column will never be
populated because of an off-by-one error.
Index: src/setup.c
==
--- src/setup.c
+++ src/setup.c
@@ -178,11 +178,11 @@
);
while( db_step(&s)==SQLITE_ROW ){
One of the #ifdef guards in src/utf8.c can be moved up since the
fossil_utf8_to_console() function is only ever called on WIN32
platforms anyway.
BTW, many guards are "#if defined(_WIN32)" rather than "#ifdef _WIN32"
but I'm not sure what is preferred here.
Index: src/utf8.c
In light of the new wiki article:
https://www.fossil-scm.org/index.html/wiki?name=Fossil-NG
I suggest not getting too carried away with adding features after
features. Most of the stuff here seems good, but everything under
"Support For Multiple VCS Formats" seems unnecessary.
Fossil sho
Hello Stephan,
On Sun, 12 Nov 2017 15:45:37 +0100
Stephan Beal wrote:
> i'm the original developer of the JSON API, but a severe, long-term
> case of RSI (since Dec. 2014) has forced me to retire from my open
> source work (except for occasional tiny patches), thus i don't
> personally work on it
Good day to you all,
I have been trying to find up-to-date information about the JSON API
built into Fossil. Is there any plans on moving forward with this?
The latest information I could find is a link to a document on Google
Docs in a mail dated back in 2013 or so, and I cannot tell when the
do
30 matches
Mail list logo
