On Fri, Sep 02, 2011 at 01:13:43PM +1000, Steve Bennett wrote:
On 02/09/2011, at 7:43 AM, Lluís Batlle i Rossell wrote:
Does the autosetup detect 'readline' for all of you?
For me, it says that it cannot find the 'readline' symbol in the lib.
In my case, autosetup is even not
On Fri, Sep 02, 2011 at 06:15:54PM +1000, Steve Bennett wrote:
Thanks. Can you test this patch for me it see if it helps?
Now it outputs:
Checking for zlib.h...ok
Checking libs for inflateEnd...-lz
Checking for system ssl...ok
HTTP support enabled
Checking for readline/readline.h...Checking
On 02/09/2011, at 6:24 PM, Lluís Batlle i Rossell wrote:
On Fri, Sep 02, 2011 at 06:15:54PM +1000, Steve Bennett wrote:
Thanks. Can you test this patch for me it see if it helps?
Now it outputs:
Checking for zlib.h...ok
Checking libs for inflateEnd...-lz
Checking for system ssl...ok
Well, you could just do this (see attached patch).
Thanks!
But should it be restricted to when compiling http_ssl? To Mac OS X? To 10.7?
I think restricting it to just Mac OS X is okay.
We know that they deprecated OpenSSL, and we don't have any plans to do
something with it apart from
After doing 'make clean', './configure' complains that 'Makefile.in'
doesn't exist (and indeed it doesn't)
Seem to be deleted by merge here:
http://www.fossil-scm.org/index.html/info/e4f1c1fe95
--
Dmitry Chestnykh
___
fossil-users mailing list
I was curious about this too. Seems they're replacing it with Common Crypto:
http://ludovicrousseau.blogspot.com/2011/08/mac-os-x-lion-and-openssl.html
Yeah, the big warnings are mostly for App Store developers. They (including me
:) have to statically compile OpenSSL or use Common Crypto,
On 02/09/2011, at 6:24 PM, Lluís Batlle i Rossell wrote:
On Fri, Sep 02, 2011 at 06:15:54PM +1000, Steve Bennett wrote:
Thanks. Can you test this patch for me it see if it helps?
Now it outputs:
Checking for zlib.h...ok
Checking libs for inflateEnd...-lz
Checking for system ssl...ok
On 02/09/2011, at 7:27 PM, Dmitry Chestnykh wrote:
Well, you could just do this (see attached patch).
Thanks!
But should it be restricted to when compiling http_ssl? To Mac OS X? To 10.7?
I think restricting it to just Mac OS X is okay.
We know that they deprecated OpenSSL, and we
On Sep 2, 2011, at 11:28 AM, Dmitry Chestnykh wrote:
After doing 'make clean', './configure' complains that 'Makefile.in'
doesn't exist (and indeed it doesn't)
Seem to be deleted by merge here:
http://www.fossil-scm.org/index.html/info/e4f1c1fe95
I'm wrong, earlier:
OK. So this should do then.
Thank you!
--
Dmitry Chestnykh
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/01/2011 06:17 PM, Stephan Beal wrote:
Regarding the comparison with git: git tracks changes differently, and can
even tell you that a given commit moved X lines of code from file A to file
B (it's pretty f-ing smart that way). Fossil tracks
Hello,
I tried to write this in a commit comment:
# First Item
# Second item
And fossil thought those were comments to be ignored.
Couldn't fossil simply ignore the lines with '#' as first character? or that has
some disadvantadges?
Thank you!
On Fri, 2 Sep 2011 18:15:47 +0200
Lluís Batlle i Rossell virik...@gmail.com wrote:
I tried to write this in a commit comment:
# First Item
# Second item
And fossil thought those were comments to be ignored.
Couldn't fossil simply ignore the lines with '#' as first character?
or
Would it be possible to add this feature, at least for making
tickets older than the date they were entered? Is there a strong
reason to disallow the editing of time stamps on tickets?
For my $0.02, I think adding such a feature would require a fair development
effort. You'd need to have UI
On Fri, Sep 02, 2011 at 07:43:21PM +1000, Steve Bennett wrote:
On 02/09/2011, at 6:24 PM, Lluís Batlle i Rossell wrote:
It looks like it is not testing the symbol anymore.
OK. Try this fix instead.
It works, thank you!
I use tclsh, because that's the only way to be able to run make test
At a complete loss.
This is what i get every time, no matter what i do. Perhaps there is
some fundamental thing i am not understanding.
rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push
Server:http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/
via proxy:
On Fri, Sep 02, 2011 at 01:44:51PM -0400, ron georgia wrote:
At a complete loss.
This is what i get every time, no matter what i do. Perhaps there is
some fundamental thing i am not understanding.
rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push
Server:
Thanks James (or Jim) - but here is what i get:
rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push
http://rgeor...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker
password for rgeorgia:
via proxy: http://proxy.gslb.alcatel-lucent.com:8000
Bytes Cards Artifacts
O! Got it! I removed the proxy. fossil set proxy off. Now i use my
local proxy setting.
rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push
http://rgeor...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/
password for rgeorgia:
Bytes Cards Artifacts Deltas
On Fri, Sep 2, 2011 at 1:02 PM, Clark Christensen cdcmi...@yahoo.com wrote:
FWIW, Fossil does allow you to add fields to the ticket table, markup to the
ticket create/edit/view pages, and customize the ticket reports. So it
seems like you could add your own field for storing your custom
At 11:10 AM 9/2/2011, Ron Wilson wrote:
On Fri, Sep 2, 2011 at 1:02 PM, Clark Christensen wrote:
FWIW, Fossil does allow you to add fields to the ticket table,
markup to the ticket create/edit/view pages, and customize the
ticket reports.
Yes, I've added custom fields to tickets and made
How many tickets are we talking about? If it is only a few then perhaps try
the following:
# Set your system date to the date for the ticket
sudo date -s 08/11/2011
# create the ticket
fossil ui
# repeat for remaining tickets
Maybe do it in a virtualbox instance just be sure to put the date
On Fri, Sep 2, 2011 at 9:48 PM, Matt Welland estifo...@gmail.com wrote:
# Set your system date to the date for the ticket
sudo date -s 08/11/2011
Beware with that - it can confuse your build system.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
We are revisiting fossil for use in our team and I've been doing a little
performance testing. One thing that we've seen is when two people access the
central repo simultaneously sometimes sync can fail and you get the
continue without sync: y/N question. This is benign enough and recovery is
On Fri, Sep 2, 2011 at 5:17 PM, Matt Welland estifo...@gmail.com wrote:
We are revisiting fossil for use in our team and I've been doing a little
performance testing. One thing that we've seen is when two people access the
central repo simultaneously sometimes sync can fail and you get the
On Thu, Sep 01, 2011 at 07:43:56PM +0200, Dmitry Chestnykh wrote:
My simple performance test of SHA-1 from checkin [f2ede7da6d] vs
OpenSSL shows that the latter is a bit faster:
When I ported the NetBSD implementation, I was considering using
OpenSSL. The discussion with Richard was essentially
On Thu, Sep 01, 2011 at 12:53:45PM -0400, Martin S. Weber wrote:
Sadly if you clone with http://USER@host/...my.fsl and enter the
password in the prompt, it will *not* remember the password (at
least last time I tried).
You can use USER:PASSWOR@host.
Joerg
27 matches
Mail list logo
