2014-05-30 22:25 GMT+02:00 Stephan Beal sgb...@googlemail.com:
On Fri, May 30, 2014 at 10:15 PM, Stephan Beal sgb...@googlemail.com
wrote:
H. It seems fossil no longer has an option to create the initial
checkin, and i can't figure out how to create one without libfossil:
There are
On 31 May 2014 21:40, Stephan Beal sgb...@googlemail.com wrote:
On Sat, May 31, 2014 at 4:33 PM, Stephan Beal sgb...@googlemail.com wrote:
Once i'm back from shopping i'll work on a patch which reverts to
...
i've implemented the above. It looks something like:
...
Thanks a lot. As you
On Sun, Jun 1, 2014 at 9:26 AM, Michai Ramakers m.ramak...@gmail.com
wrote:
Thanks a lot. As you already suggested, initial checkin now being the
default again, the initial-checkinless feature will probably receive
precious little testing, let alone from new users. /obvious
It will from me,
On 31 May 2014 02:14, Andy Bradford amb-fos...@bradfords.org wrote:
Thus said Michai Ramakers on Fri, 30 May 2014 21:06:36 +0200:
michai@main:~/proj/081/adm$ f ci -m 'added note about spent time'
time_spent.txt
New_Version: 187aa4a7c8b1377ddf05b1d979afe89adeff8dc0
working checkout does not
On Fri, May 30, 2014 at 8:14 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
Looks like this is due to the recent addition of the empty initial
checkin in [cac91b6cd17ab746]:
Can somebody please explain to me what this change accomplishes, other that
introduce needless bugs, which it
Thus said Stephan Beal on Sat, 31 May 2014 16:33:48 +0200:
i would personally like to see it kept (mainly for future
compatibility with libfossil, which doesn't require an initial checkin
;), but not as the default. The default should stay as it historically
has been - creating
On Sat, May 31, 2014 at 5:57 PM, Andy Bradford amb-fos...@bradfords.org
wrote:
Regarding the error, if I understand the R-card, it seems like the
manifest checksum is wrong:
$ f ci -n -m one file
F file 2464bdd2457e7e5aba5e76138b6bbb31416bc894
R bd4b079b9dbaf9228c7174fc4675292e
You
On Sat, May 31, 2014 at 4:33 PM, Stephan Beal sgb...@googlemail.com wrote:
On Sat, May 31, 2014 at 1:21 PM, Richard Hipp d...@sqlite.org wrote:
Can somebody please explain to me what this change accomplishes, other
that introduce needless bugs, which it seems to excel at? What problem
does
On Sat, May 31, 2014 at 6:49 PM, Stephan Beal sgb...@googlemail.com wrote:
Am i wrong, or did Joel's patch just correct the problem:
For completeness:
[stephan@host:~/tmp/x]$ f-acat rid:3
C egg
D 2014-05-31T16:47:37.137
F a 9f2f5f07e9326b68b448f9b452a14f63cfadc27c
F b
Stephan Beal wrote:
Am i wrong, or did Joel's patch just correct the problem:
I hope so. The commit I backed out seems to serve no purpose besides
messing up vfile_aggregate_checksum_disk(). Specifically, this part from
the function's documentation:
** Newly added files that are not
Thus said Stephan Beal on Sat, 31 May 2014 18:49:09 +0200:
Am i wrong, or did Joel's patch just correct the problem:
Yes, it does appear to correct it:
$ ../fossil ver
This is fossil version 1.29 [1a0179abd7] 2014-05-31 16:37:06 UTC
$ ../fossil info | grep checkins
checkins: 0
$ jot -w
On 31 May 2014 18:49, Stephan Beal sgb...@googlemail.com wrote:
Am i wrong, or did Joel's patch just correct the problem:
seems to work here too, with some simple examples.
Michai
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On Sat, May 31, 2014 at 4:33 PM, Stephan Beal sgb...@googlemail.com wrote:
Once i'm back from shopping i'll work on a patch which reverts to the
previous default behaviour and adds a new flag for those who want to
create/play with an empty repo (which still likely has open corner cases
On Sat, May 31, 2014 at 9:40 PM, Stephan Beal sgb...@googlemail.com wrote:
[stephan@host:~/tmp]$ f-timeline -R x3.fsl
checkin [e63f7616798d] @ 2010-01-01 02:02:03 by [stephan] branch [trunk]
initial empty check-in
Hmmm (unrelated)... timestamp doesn't take into account summer time diff.
Stephan - i'm on mobile ATM so will be brief, but you and I did discussed
this offline weeks ago whereby I thought we agreed that changing the text
of the initial commit to something symbolic (.?) or inoffensive Latin
(seed , origin) really would fit the bill without rejigging core fossil
Also briefly from the tablet (in bed)... the current impl maintains the
historical behaviour by default, while making the new behaviour available
via a flag (-empty, though feel free to suggest a name). Will look through
my chat logs tomorrow - our discussion was there, i think.
(sent from a
Hello,
some weirdness I have not seen before:
michai@main:~/proj/081/adm$ f changes
ADDED time_spent.txt
ADDED ../comm/20140530_sent_to_ec/indicator-B_Cu.pho
ADDED ../comm/20140530_sent_to_ec/indicator-B_Mask.pho
ADDED ../comm/20140530_sent_to_ec/indicator-Edge_Cuts.pho
ADDED
and...
michai@main:~/proj/081$ f timeline
+++ no more data (0) +++
This is a brand new repo; indeed there are no checkins.
Michai
On 30 May 2014 21:06, Michai Ramakers m.ramak...@gmail.com wrote:
Hello,
some weirdness I have not seen before:
michai@main:~/proj/081/adm$ f changes
ADDED
Is the offending file a symbolic link?
On Fri, May 30, 2014 at 3:11 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
and...
michai@main:~/proj/081$ f timeline
+++ no more data (0) +++
This is a brand new repo; indeed there are no checkins.
Michai
On 30 May 2014 21:06, Michai Ramakers
On 30 May 2014 21:13, Richard Hipp d...@sqlite.org wrote:
Is the offending file a symbolic link?
no:
-rw-r--r-- 1 michai users 163 May 30 20:42 time_spent.txt
nor are there any symlinks in the path leading to the file or repo.
If interested: the repo is about 53 kB; I could mail it for
On 30 May 2014 21:13, Richard Hipp d...@sqlite.org wrote:
Is the offending file a symbolic link?
I don't think it's the contents of this or the other files causing this:
michai@main:~/proj/081$ echo kiwi kiwi
michai@main:~/proj/081$ f add kiwi
ADDED kiwi
michai@main:~/proj/081$ f ci -m
On Fri, May 30, 2014 at 3:23 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
On 30 May 2014 21:13, Richard Hipp d...@sqlite.org wrote:
Is the offending file a symbolic link?
I don't think it's the contents of this or the other files causing this:
michai@main:~/proj/081$ echo kiwi kiwi
On 30 May 2014 21:27, Richard Hipp d...@sqlite.org wrote:
The proximal cause of the error message is the pre-commit sanity checks that
Fossil runs on each check-in. (See
http://www.fossil-scm.org/fossil/doc/tip/www/selfcheck.wiki for details.)
Fossil is looking at the files it is about to
On Fri, May 30, 2014 at 9:11 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
michai@main:~/proj/081$ f timeline
+++ no more data (0) +++
This is a brand new repo; indeed there are no checkins.
*cough* this looks _exactly_ like a bug we had recently involving the rid 0
(no checkins) case. i
On Fri, May 30, 2014 at 9:23 PM, Michai Ramakers m.ramak...@gmail.com
wrote:
On 30 May 2014 21:13, Richard Hipp d...@sqlite.org wrote:
Is the offending file a symbolic link?
I don't think it's the contents of this or the other files causing this:
michai@main:~/proj/081$ echo kiwi kiwi
On 30 May 2014 22:25, Stephan Beal sgb...@googlemail.com wrote:
On Fri, May 30, 2014 at 10:15 PM, Stephan Beal sgb...@googlemail.com
wrote:
Is this repo _completely_ empty (no initial checkin)? If so, please
recreate it with an initial empty checkin and i'll bet my left leg the
problem goes
Thus said Michai Ramakers on Fri, 30 May 2014 21:06:36 +0200:
michai@main:~/proj/081/adm$ f ci -m 'added note about spent time'
time_spent.txt
New_Version: 187aa4a7c8b1377ddf05b1d979afe89adeff8dc0
working checkout does not match what would have ended up in the
repository:
Thus said Stephan Beal on Fri, 30 May 2014 22:25:30 +0200:
H. It seems fossil no longer has an option to create the initial
checkin.
It does using the --date-override option:
fossil new --date-override '2014-05-30 00:00:00' test.fossil
Will create a new fossil with an initial empty
On Mon, 19 Nov, Richard Hipp wrote:
Fossil compresses files using zlib (and delta compression if other
similar files are available) and stores the result as an SQLite
BLOB. The maximum size of an SQLite BLOB is 1GiB. So, unless the
4GiB file compresses well, it is not a candidate for being
Hi all,
following up with my other question regarding backslashes in filenames,
I now just removed that file in question and wanted to proceed with my
svn-fossil conversion:
$ cd svn_working_copy
$ fossil init myproject.fossil
$ fossil open --keep myproject.fossil
$ fossil addremove
[...]
added
On Mon, Nov 19, 2012 at 6:40 AM, Stefan Bellon sbel...@sbellon.de wrote:
Hi all,
following up with my other question regarding backslashes in filenames,
I now just removed that file in question and wanted to proceed with my
svn-fossil conversion:
$ cd svn_working_copy
$ fossil init
On Mon, 19 Nov, Richard Hipp wrote:
Can you figure out which of the 37594 added files is causing the
problem?
I would have hoped fossil can tell me using some --verbose option. If
not, I'll try to binary search for the offending file.
Greetings,
Stefan
--
Stefan Bellon
On Mon, Nov 19, 2012 at 7:41 AM, Stefan Bellon sbel...@sbellon.de wrote:
On Mon, 19 Nov, Richard Hipp wrote:
Can you figure out which of the 37594 added files is causing the
problem?
I would have hoped fossil can tell me using some --verbose option. If
not, I'll try to binary search for
On Mon, 19 Nov, Richard Hipp wrote:
Clearly I've overlooked something. If you can give me some idea of
what is missing, I'll fix it.
I found out what is causing this: I had a log file of over 4 GB size
(4376612120 bytes to be precise) in one of the sub directories.
Removing that file made the
On Mon, Nov 19, 2012 at 9:22 AM, Stefan Bellon sbel...@sbellon.de wrote:
On Mon, 19 Nov, Richard Hipp wrote:
Clearly I've overlooked something. If you can give me some idea of
what is missing, I'll fix it.
I found out what is causing this: I had a log file of over 4 GB size
(4376612120
35 matches
Mail list logo
