Hello,
On Thu, Jan 10, 2013 at 1:03 AM, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Wed, Jan 09, 2013 at 05:02:14PM +, Michai Ramakers wrote:
apart from the question whether cloning from localhost makes sense or
not (I use this from a script to make work from localhost or remote
I didn't know the 'analyze' sqlite command, thank you. When trying (I
am assuming you meant with '-R' option to point to repo), I got
slightly more than I bargained for:
[...]
Segmentation fault (core dumped)
Retried with newer fossil-version [c7133bd79d] from yesterday, and
segfault is
On Thu, Jan 10, 2013 at 10:19:31AM +, Michai Ramakers wrote:
Hello,
On Thu, Jan 10, 2013 at 1:03 AM, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
On Wed, Jan 09, 2013 at 05:02:14PM +, Michai Ramakers wrote:
apart from the question whether cloning from localhost makes sense or
On Thu, Jan 10, 2013 at 11:22 AM, Joerg Sonnenberger I didn't know
the 'analyze' sqlite command, thank you. When trying (I
am assuming you meant with '-R' option to point to repo), I got
slightly more than I bargained for:
[snip]
Heh, that's for drh. You said sqlite analyze works? Does it
On Thu, Jan 10, 2013 at 11:22 AM, Joerg Sonnenberger
jo...@britannica.bec.de wrote:
Heh, that's for drh. You said sqlite analyze works? Does it help or not?
Also... see
http://www.fossil-scm.org/xfer/info/85233c40c9bb05a87574cdc25402ec0d34b0b7ee
: queries seem to be optimised to run without
hi,
I would find it useful if `fossil info' (or `stat', `timeline', or a new
command) would provide a means/option to show the total number of
revisions (by default or optional), more precisely, the number of file
commits (as it is called in `fossil help timeline) in the repo. the
On Thu, Jan 10, 2013 at 12:32 PM, Michai Ramakers m.ramak...@gmail.comwrote:
ah yes... forgot that :) It does not help. Note that taking 1 cpu core
offline ('cpuctl offline 1' here) makes it fly
This is just pure speculation, but ... perhaps there is a problem in BSD
multi-core cases, such
On Thu, Jan 10, 2013 at 12:56 PM, j. van den hoff veedeeh...@googlemail.com
wrote:
I would find it useful if `fossil info' (or `stat', `timeline', or a new
command) would provide a means/option to show the total number of revisions
(by default or optional), more precisely, the number of file
Hi, all,
i just coincidentally saw this on the /stat page of the main fossil repo:
Duration Of Project:2000 days or approximately 5.48 years.
Happy 2000th day, Fossil!
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
On Thu, Jan 10, 2013 at 1:35 PM, Stephan Beal sgb...@googlemail.com wrote:
i'll sign up for adding that - i would be able to do this on Sunday. i
would add it to the status command because we have that info in the /stat
page already (and in fossil json stat -full).
Don't tell my boss this,
On Thu, 10 Jan 2013 13:21:50 +0100
Stephan Beal sgb...@googlemail.com wrote:
On Thu, Jan 10, 2013 at 12:32 PM, Michai Ramakers m.ramak...@gmail.comwrote:
ah yes... forgot that :) It does not help. Note that taking 1 cpu core
offline ('cpuctl offline 1' here) makes it fly
This is just
On Thu, 10 Jan 2013 13:35:06 +0100, Stephan Beal sgb...@googlemail.com
wrote:
On Thu, Jan 10, 2013 at 12:56 PM, j. van den hoff
veedeeh...@googlemail.com
wrote:
I would find it useful if `fossil info' (or `stat', `timeline', or a new
command) would provide a means/option to show the
On Thu, Jan 10, 2013 at 1:53 PM, Eduardo Morras emorr...@yahoo.es wrote:
If he tries in shell 1
fossil open repository
fossil server
and in shell 2
fossil clone http://localhost:8080/ copy.fossil
should workaround it, the repository is opened only once
In theory, yes, but the web
On Thu, Jan 10, 2013 at 1:57 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
...works like a charm and saves lots of typing (locally chronological rev.
nums are much easier to memorize (and to type...) than sha1 hashes).
so I still think this would be useful.
Explained that way it does
On Thu, 10 Jan 2013 14:12:18 +0100
Stephan Beal sgb...@googlemail.com wrote:
On Thu, Jan 10, 2013 at 1:57 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
...works like a charm and saves lots of typing (locally chronological rev.
nums are much easier to memorize (and to type...) than
On Wed, Jan 2, 2013 at 4:12 PM, Richard Hipp d...@sqlite.org wrote:
On Wed, Jan 2, 2013 at 3:58 PM, Ruediger Haertel r_haer...@gmx.de wrote:
Hello,
happy new year to all of you. Will there be precompiled versions of v1.25?
I
remember there was a discussion about this, but don't know what
https://chiselapp.com/user/nico/repository/nico
Two branches: rebase, and test-rebase.
This adds a --nocommit option to the fossil merge command that does...
what it sounds like it does: it applies the patch from a --cherrypick
commit and leaves that uncommitted.
I applied all the commits from
On Thu, 10 Jan 2013 13:51:51 +0100, Stephan Beal sgb...@googlemail.com
wrote:
On Thu, Jan 10, 2013 at 1:35 PM, Stephan Beal sgb...@googlemail.com
wrote:
i'll sign up for adding that - i would be able to do this on Sunday. i
would add it to the status command because we have that info in
I don't understand: fossil merge has never done a commit. The --nocommit
option seems like a noop to me. What am I misunderstanding?
D. Richard Hipp - d...@sqlite.org
Sent from phone - pardon brevity
On Jan 10, 2013 10:19 AM, Nico Williams n...@cryptonector.com wrote:
Hello,
it would be nice if the Tags and Branches ui pages had something more than the
names listed. For example, next to each, could be the date of the head or the
last commit referred to.
What do you think?
Regards,
Lluís.
___
fossil-users mailing
On Thu, 10 Jan 2013 13:51:51 +0100, Stephan Beal sgb...@googlemail.com
wrote:
On Thu, Jan 10, 2013 at 1:35 PM, Stephan Beal sgb...@googlemail.com
wrote:
i'll sign up for adding that - i would be able to do this on Sunday. i
would add it to the status command because we have that info in
This number is the same one reported from the /stat page for number of
commits. i am not sure off-hand whether wiki edits and whatnot are
included.
(sent from phone from dentist office...)
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
On Jan 10, 2013 5:24 PM,
For anyone else interested, here are the steps for building fossil.exe
with OpenSSL support on a FreeBSD host (9.0-RELEASE-p5 amd64):
1. Install devel/mingw32-gcc, devel/mingw32-zlib, and
devel/mingw32-openssl ports. As of this writing, mingw32-zlib (1.2.5)
fails to build due to a problem with
Hello.
It seems as though it's only really possible to sync to one remote
server at a time. Is there a way to specify that a repository should
push to multiple remote servers?
My use case here is that I've got repositories hosted on
http://fossil.io7m.com but I've also got an exact mirror of
Hi Folks,
Just starting to experiment with Fossil for use on a project, and I'd
like to use it for documentation as well as code. As I've been playing
with the wiki and embedded documentation features, I've noticed a few
things that lead to a few questions. Advice would be most welcomed:
25 matches
Mail list logo
