Discussion:
Fossil version 1.21
(too old to reply)
Richard Hipp
2011-12-13 14:29:14 UTC
Permalink
Fossil version 1.21 has been packaged and put on the website for convenient
download. See http://www.fossil-scm.org/download.html for details
including a summary of changes since the previous release.

Please let me know if you encounter any problems with this release. Thanks.
--
D. Richard Hipp
***@sqlite.org
Dmitry Chestnykh
2011-12-13 14:41:00 UTC
Permalink
Post by Richard Hipp
Fossil version 1.21 has been packaged and put on the website for
convenient download. See http://www.fossil-scm.org/download.html for
details including a summary of changes since the previous release.
On this page, the link "See the Change Log for additional details"
leads to the previous version of changes.wiki. The correct one is:

http://www.fossil-scm.org/fossil/doc/489c67ae46/www/changes.wiki
--
Dmitry Chestnykh
http://www.codingrobots.com
Tomek Kott
2011-12-13 14:58:02 UTC
Permalink
With the new TCL integration, does that mean that full TCL support is
available through the server end as well? That is, currently we can use TH1
variables etc. when setting up the displays, tickets, etc. through the web
interface. With TCL enabled, can we now replace the TH1 with TCL?

Thanks,

Tomek

On Tue, Dec 13, 2011 at 9:41 AM, Dmitry Chestnykh
Post by Dmitry Chestnykh
Post by Richard Hipp
Fossil version 1.21 has been packaged and put on the website for
convenient download. See http://www.fossil-scm.org/download.html for
details including a summary of changes since the previous release.
On this page, the link "See the Change Log for additional details"
http://www.fossil-scm.org/fossil/doc/489c67ae46/www/changes.wiki
--
Dmitry Chestnykh
http://www.codingrobots.com
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Joe Mistachkin
2011-12-13 23:30:16 UTC
Permalink
Post by Tomek Kott
With the new TCL integration, does that mean that full TCL support is
available through the server end as well?
Yes.
Post by Tomek Kott
That is, currently we can use TH1 variables etc. when setting up the
displays, tickets, etc. through the web interface.
Post by Tomek Kott
With TCL enabled, can we now replace the TH1 with TCL?
The Tcl language does not replace TH1, it augments it. For example, when
Tcl support is enabled at compile-time and
runtime (via the new "tcl" setting), you can use the [tclEval], [tclExpr],
and [tclInvoke] commands to allow complete
access to Tcl from TH1. Similarly, the created Tcl interpreter will contain
the [th1Eval] and [th1Expr] commands to
allow Tcl script access to the Fossil-specific functionality already exposed
to TH1.

The Tcl integration was done in this way to maintain maximum compatibility
with previous versions and to allow people to
stick with using TH1 if they feel that Tcl is too 'heavy' for their
environment.

Here is a quick example TH1 script taken from the tests for the new Tcl
integration feature:

tclInvoke set repository_name [repository 1]
proc doOut {msg} {puts $msg; puts \n}
doOut [tclEval {
package require sqlite3
sqlite3 db $repository_name
set x [db eval {SELECT COUNT(*) FROM user;}]
db close
return $x
}]

--
Joe Mistachkin
Steve Bennett
2011-12-14 00:42:44 UTC
Permalink
Post by Tomek Kott
Post by Tomek Kott
With the new TCL integration, does that mean that full TCL support is
available through the server end as well?
Yes.
Post by Tomek Kott
That is, currently we can use TH1 variables etc. when setting up the
displays, tickets, etc. through the web interface.
Post by Tomek Kott
With TCL enabled, can we now replace the TH1 with TCL?
As Joe says, Tcl is in addition to TH1.
Note that the 'jimtcl' branch does replace TH1 with Jim Tcl, and of course
maintains support for calling out to "big" Tcl.

Cheers,
Steve

--
µWeb: Embedded Web Framework - http://uweb.workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au P: +61 434 921 300
E: ***@workware.net.au F: +61 7 3391 6002
Chad Perrin
2011-12-13 16:52:04 UTC
Permalink
Post by Richard Hipp
Fossil version 1.21 has been packaged and put on the website for convenient
download. See http://www.fossil-scm.org/download.html for details
including a summary of changes since the previous release.
Mentioned on @CopyfreeNews:

http://twitter.com/#!/CopyfreeNews/status/146632792241995776

Point of curiosity: Is there a Twitter feed for Fossil?
Richard Hipp
2011-12-13 16:56:42 UTC
Permalink
Post by Chad Perrin
Point of curiosity: Is there a Twitter feed for Fossil?
I was thinking the other day that it might be cool to have a feature
whereby a Fossil server would tweet every time it got a new check-in or
ticket or wiki edit, etc. Any volunteers to contribute code?
--
D. Richard Hipp
***@sqlite.org
Konstantin Khomoutov
2011-12-13 17:12:07 UTC
Permalink
On Tue, 13 Dec 2011 11:56:42 -0500
Post by Richard Hipp
Post by Chad Perrin
Point of curiosity: Is there a Twitter feed for Fossil?
I was thinking the other day that it might be cool to have a feature
whereby a Fossil server would tweet every time it got a new check-in
or ticket or wiki edit, etc. Any volunteers to contribute code?
Why tweet? This is a proprietary service for little girls and
housewives. Providing an RSS feed on relevant pages (timeline, namely)
would be just right (some wiki engines do this for their "changes" page
for instance).
Jeremy Cowgar
2011-12-13 17:14:19 UTC
Permalink
There is already an RSS feed, project.org/timeline.rss.

As for Twitter being for little girls and housewives, millions of people
disagree :-)

Jeremy

-----Original Message-----
From: Konstantin Khomoutov
Sent: Tuesday, December 13, 2011 12:12 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Fossil version 1.21

On Tue, 13 Dec 2011 11:56:42 -0500
Post by Richard Hipp
Post by Chad Perrin
Point of curiosity: Is there a Twitter feed for Fossil?
I was thinking the other day that it might be cool to have a feature
whereby a Fossil server would tweet every time it got a new check-in
or ticket or wiki edit, etc. Any volunteers to contribute code?
Why tweet? This is a proprietary service for little girls and
housewives. Providing an RSS feed on relevant pages (timeline, namely)
would be just right (some wiki engines do this for their "changes" page
for instance).
Chad Perrin
2011-12-14 01:24:37 UTC
Permalink
Post by Jeremy Cowgar
There is already an RSS feed, project.org/timeline.rss.
As for Twitter being for little girls and housewives, millions of
people disagree :-)
I believe Twitter will turn out to be a passing fad (though it might take
a few years to get to that point). In the meantime, though, its
widespread use (including amongst software developers -- it's huge in the
Rails community, for instance) suggests that one would be wise to take
advantage of its marketing value while it remains relevant, in at least
some cases.

Nolan Darilek
2011-12-13 17:17:53 UTC
Permalink
Not to beat a dead horse, but this seems like a great use for hooks.

I'd rather Fossil ping a CI server like Jenkins rather than tweet when a
change gets made.
Post by Chad Perrin
Point of curiosity: Is there a Twitter feed for Fossil?
I was thinking the other day that it might be cool to have a feature
whereby a Fossil server would tweet every time it got a new check-in
or ticket or wiki edit, etc. Any volunteers to contribute code?
--
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Ben Summers
2011-12-13 17:18:27 UTC
Permalink
Post by Chad Perrin
Point of curiosity: Is there a Twitter feed for Fossil?
I was thinking the other day that it might be cool to have a feature whereby a Fossil server would tweet every time it got a new check-in or ticket or wiki edit, etc. Any volunteers to contribute code?
That sounds like a post-commit hook to me.

Ben


--
http://bens.me.uk/
Stephan Beal
2011-12-13 17:28:27 UTC
Permalink
Post by Ben Summers
That sounds like a post-commit hook to me.
FYIW: this type of post-commit hook could be implemented on top of the JSON
API, with the caveat that there would be a delay - the hook would have to
poll and store enough state to be able to decide whether a given commit is
new or not.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
Matt Welland
2011-12-13 17:33:43 UTC
Permalink
The changes include: "Stop showing the server-code in status outputs - it
is no longer used for anything."

I've been using the server code extracted with "fossil info" to uniquely
identify repos. Is there a new way? I assume that the server code itself
continues to exist?
Post by Richard Hipp
Fossil version 1.21 has been packaged and put on the website for
convenient download. See http://www.fossil-scm.org/download.html for
details including a summary of changes since the previous release.
Please let me know if you encounter any problems with this release. Thanks.
--
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Richard Hipp
2011-12-13 17:43:32 UTC
Permalink
Post by Matt Welland
The changes include: "Stop showing the server-code in status outputs - it
is no longer used for anything."
I've been using the server code extracted with "fossil info" to uniquely
identify repos. Is there a new way? I assume that the server code itself
continues to exist?
The server-code is still there. It just isn't used for anything.

Perhaps you want the project-code, which is unique for a project. All
servers that sync against that project share the same project-code, but
different projects have different codes.

The project code for Fossil itself is
CE59BB9F186226D80E49D1FA2DB29F935CCA0333 and all of the Fossil mirrors know
that. SQLite, on the other hand uses a project code of
2ab58778c2967968b94284e989e43dc11791f548 which is different. That way, you
cannot accidently "sync" a Fossil repo with an SQLite repo.
Post by Matt Welland
Post by Richard Hipp
Fossil version 1.21 has been packaged and put on the website for
convenient download. See http://www.fossil-scm.org/download.html for
details including a summary of changes since the previous release.
Please let me know if you encounter any problems with this release. Thanks.
--
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
D. Richard Hipp
***@sqlite.org
Matt Welland
2011-12-13 17:59:21 UTC
Permalink
Post by Richard Hipp
Post by Matt Welland
The changes include: "Stop showing the server-code in status outputs - it
is no longer used for anything."
I've been using the server code extracted with "fossil info" to uniquely
identify repos. Is there a new way? I assume that the server code itself
continues to exist?
The server-code is still there. It just isn't used for anything.
Perhaps you want the project-code, which is unique for a project. All
servers that sync against that project share the same project-code, but
different projects have different codes.
Ah yes, in fact I was using the project code for identifying the repo. My
mistake on confusing project and server when I read the release notes. Now
that I know what server code is I understand the lack of need for showing
it. Thanks.
Post by Richard Hipp
The project code for Fossil itself is
CE59BB9F186226D80E49D1FA2DB29F935CCA0333 and all of the Fossil mirrors know
that. SQLite, on the other hand uses a project code of
2ab58778c2967968b94284e989e43dc11791f548 which is different. That way, you
cannot accidently "sync" a Fossil repo with an SQLite repo.
Post by Matt Welland
Post by Richard Hipp
Fossil version 1.21 has been packaged and put on the website for
convenient download. See http://www.fossil-scm.org/download.html for
details including a summary of changes since the previous release.
Please let me know if you encounter any problems with this release. Thanks.
--
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Carlo Miron
2011-12-13 20:01:31 UTC
Permalink
Post by Richard Hipp
Fossil version 1.21 has been packaged and put on the website for convenient
download.  See http://www.fossil-scm.org/download.html for details including
a summary of changes since the previous release.
Please let me know if you encounter any problems with this release. Thanks.
Out of curiosity: why is the Linux executable (and only that) over
than doubled in size?
Is it "more statically linked" than the other binaries?

Thanks,
©
--
Carlo Miron
Open Source Solution Architect
Richard Hipp
2011-12-13 20:03:33 UTC
Permalink
Post by Richard Hipp
Post by Richard Hipp
Fossil version 1.21 has been packaged and put on the website for
convenient
Post by Richard Hipp
download. See http://www.fossil-scm.org/download.html for details
including
Post by Richard Hipp
a summary of changes since the previous release.
Please let me know if you encounter any problems with this release.
Thanks.
Out of curiosity: why is the Linux executable (and only that) over
than doubled in size?
Is it "more statically linked" than the other binaries?
Right. The linux binary is statically linked. The others all use system
libraries (which we can better get away with because there is more
consistency about which libraries are available on non-linux systems.)
Post by Richard Hipp
Thanks,
©
--
Carlo Miron
Open Source Solution Architect
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
D. Richard Hipp
***@sqlite.org
Continue reading on narkive:
Loading...