Hello
Am I correct in understanding that this is the right way to proceed to
try some new code, and either save it (whether it works or not, just
as a track-record) or discard it?
To try some new code:
1. Commit current code
2. Try new code
3.
a. if OK, commit new code : fossil commit -m New
On Wed, 09 Jan 2013 12:10:35 +0100
Gilles gilles.gana...@free.fr wrote:
Hello
Am I correct in understanding that this is the right way to proceed to
try some new code, and either save it (whether it works or not, just
as a track-record) or discard it?
To try some new code:
1. Commit
On Wed, 9 Jan 2013 12:23:23 +0100, Eduardo Morras
emorr...@yahoo.es wrote:
2. Try new code
If in your step 2 you add/remove/move files you should fossil addremove
before the commit.
Thanks for the tip. I usually only make changes to existing files,
usually just localized changes in a single
On Wed, Jan 9, 2013 at 6:10 AM, Gilles gilles.gana...@free.fr wrote:
Hello
Am I correct in understanding that this is the right way to proceed to
try some new code, and either save it (whether it works or not, just
as a track-record) or discard it?
To try some new code:
1. Commit current
Hello,
Much nicer:
fossil add kk.cc
fossil commit -m v1
(some failed changes)
fossil commit -m failed attempt --branch failed_attempt
fossil update trunk
(some changes)
fossil commit -m good
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com
On Wed, 09 Jan 2013 12:10:35 +0100
Gilles gilles.gana...@free.fr wrote:
Am I correct in understanding that this is the right way to proceed to
try some new code, and either save it (whether it works or not, just
as a track-record) or discard it?
To try some new code:
1. Commit current code
On Wed, 9 Jan 2013 06:37:54 -0500, Richard Hipp
d...@sqlite.org wrote:
I'd do it this way:
fossil commit -m Failed Attempt --branch dead-end
fossil up prev
That will save your failed attempt in your history forever. The failed
attempt will be on a branch, however, out of the way. I avoid
On Wed, Jan 9, 2013 at 7:13 AM, Gilles gilles.gana...@free.fr wrote:
Ramon below mentions fossil update trunk instead of fossil update
prev: Does it make a difference?
Not in this case, since the previous check-in will be on trunk - they will
be the same thing.
--
D. Richard Hipp
On Wed, 9 Jan 2013 07:23:07 -0500, Richard Hipp
d...@sqlite.org wrote:
Ramon below mentions fossil update trunk instead of fossil update
prev: Does it make a difference?
Not in this case, since the previous check-in will be on trunk - they will
be the same thing.
Thank you. I'll experiment
On Tue, 08 Jan 2013 15:30:13 +0100, Gilles
gilles.gana...@free.fr wrote:
I'd like to contribute an article in the wiki, but even after logging
as anonymous, I can't see any way to add a new page:
http://www.fossil-scm.org/index.html/wcontent
Are contributions limited to non-anonymous users?
On Wed, Jan 9, 2013 at 2:34 PM, Gilles gilles.gana...@free.fr wrote:
http://www.fossil-scm.org/index.html/doc/trunk/www/permutedindex.wiki
That one's generated that way on purpose by a program. Notice that
Questions -- Frequently Asked also has 3 variants (Asked Frequently --
Question ...).
Hello,
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
transparent), I experienced very slow network traffic - but no hang -
while cloning like thus:
in shell 1: # fossil server ori.fossil
in shell 2: $
On Wed, Jan 9, 2013 at 12:02 PM, Michai Ramakers m.ramak...@gmail.comwrote:
Hello,
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
transparent), I experienced very slow network traffic - but no hang -
On Wed, Jan 9, 2013 at 12:16 PM, Michai Ramakers m.ramak...@gmail.comwrote:
Hello,
in shell 1: # fossil server ori.fossil
in shell 2: $ fossil clone http://michai@localhost:8080/ copy.fossil
Might be faster and easier to do:
fossil clone file::///path/to/ori.fossil
Michai Ramakers wrote:
[...]
...resulting in about 70 kB/s traffic with very rare (a minute or more
in between - didn't time exactly) single bursts. According to top(1),
neither server- nor client-fossils seem to be doing anything
CPU-intensive at that time.
[...]
Both 'local to local' clones
Hello,
On Wed, Jan 9, 2013 at 5:30 PM, David Given d...@cowlark.com wrote:
Michai Ramakers wrote:
[...]
...resulting in about 70 kB/s traffic with very rare (a minute or more
in between - didn't time exactly) single bursts. According to top(1),
neither server- nor client-fossils seem to be
On Wed, Jan 9, 2013 at 5:20 PM, Richard Hipp d...@sqlite.org wrote:
[...]
Would you be interested in a repo that reproduces this (here),
assuming I can make one?
Yes.
I can reproduce this with a 100 MB repo (first try - I guess it's not
the repo then :-)
I will now try to make it a bit
Michai Ramakers wrote:
[...]
Thank you for the suggestion, however:
$ /tmp/fossil clone http://michai@10.1.1.11:8080/ copy.fossil
(same result - slow)
N! My precious credibility!
Well, it's good to be able to rule that out. I have no more ideas,
unfortunately.
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ
On Wed, Jan 9, 2013 at 6:45 PM, Michai Ramakers m.ramak...@gmail.comwrote:
I will now try to make it a bit smaller for mailing. Where can I put/send
it?
This doesn't answer your question, but your question got me thinking about
using SQL to back up or vacuum repos...
On Wed, Jan 9, 2013 at 5:20 PM, Richard Hipp d...@sqlite.org wrote:
On Wed, Jan 9, 2013 at 12:16 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
Hello,
in shell 1: # fossil server ori.fossil
in shell 2: $ fossil clone http://michai@localhost:8080/ copy.fossil
Might be faster
- repo with around 2100 files, around 500 MB: reproduces 10/10 times
make that 100 MB.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
- repo with around 2100 files, around 500 MB: reproduces 10/10 times
make that 100 MB.
and 461 files... slight mixup.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Hi,
Is there an easy way with the new regex code using the regex= query parameter
for diff filtering to negate match regex? To exclude line containing
some string from the diff.
I fail to find a standard regex string on google that can do the job, I
found the 2 following regex:
Hello.
I'm working on a Fossil plugin for Jenkins (http://jenkins-ci.org), and
in order to implement the plugin, I have to query fossil repositories
in various ways.
I'm calling the fossil executables for cloning, pulling, and opening
repositories, but I'm not exactly sure what I should be doing
On Wed, Jan 9, 2013 at 3:45 PM, org.fossil-scm.fossil-us...@io7m.comwrote:
Hello.
I'm working on a Fossil plugin for Jenkins (http://jenkins-ci.org), and
in order to implement the plugin, I have to query fossil repositories
in various ways.
I'm calling the fossil executables for cloning,
On Wed, 9 Jan 2013 15:53:25 -0500
Richard Hipp d...@sqlite.org wrote:
The schema is subject to change. And years ago it would change on a
regular basis. But the schema is mostly stable now. There may be
tweaks here and there, but it mostly it will likely be the same.
The schema for the
I could not get the head to compile under solaris 10.
somehow (and this is also true for 1.24) autosetup is not capable to
pickup my openssl config.
I can do from the command line pkg-config openssl --libs and get a
correct answer.
but autosetup could not find it.
I used the
Den Wed, 09 Jan 2013 21:45:31 +0100 skrev
org.fossil-scm.fossil-us...@io7m.com:
Hello.
I'm working on a Fossil plugin for Jenkins (http://jenkins-ci.org), and
in order to implement the plugin, I have to query fossil repositories
in various ways.
I'm calling the fossil executables for
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
transparent), I experienced very slow network traffic - but no hang -
while cloning like
29 matches
Mail list logo
