On Fri, Oct 26, 2012 at 1:28 AM, K k...@lightpowered.org wrote:
On Oct 24, 2012, Ron Aaron r...@ronware.org wrote:
Wouldn't it be better to make this a parameter the user can adjust
rather than permitting any length?
While this is a more complex solution, I would support it. Perhaps in the
Hi all,
Using Fossil 1.24 on Windows, I've noticed that 'fossil clean' prompts me to
delete two files that are not reported by 'fossil extras'. A cursory look at
the Fossil code shows that while the 'extras' command uses the following:
db_multi_exec(CREATE TEMP TABLE sfile(x TEXT PRIMARY KEY
On Oct 26, 2012, Carlo Miron ca...@miron.it wrote:
On Fri, Oct 26, 2012 at 1:28 AM, K k...@lightpowered.org wrote:
On Oct 24, 2012, Ron Aaron r...@ronware.org wrote:
Wouldn't it be better to make this a parameter the user can adjust
rather than permitting any length?
While this is a more
On Fri, Oct 26, 2012 at 4:11 PM, K k...@lightpowered.org wrote:
On Oct 26, 2012, Carlo Miron ca...@miron.it wrote:
On Fri, Oct 26, 2012 at 1:28 AM, K k...@lightpowered.org wrote:
On Oct 24, 2012, Ron Aaron r...@ronware.org wrote:
Wouldn't it be better to make this a parameter the user can
Am Freitag, 26. Oktober 2012, 22:59:56 schrieb David Given:
On 26/10/12 22:42, Bernd Paysan wrote:
[...]
or try cloning it (will fail!)
Cloning worked successfully for me, on:
This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC
(standard Debian version on amd64), and
On 26/10/12 23:06, Bernd Paysan wrote:
[...]
If you have the incomplete repository, try a fossil pull, which then will
fail with an error message.
Yep, you're right, that dies:
$ fossil pull -R out.fossil
Server:http://fossil.forth-ev.de/vd-2012-03
Bytes Cards
On Fri, Oct 26, 2012 at 6:12 PM, David Given d...@cowlark.com wrote:
On 26/10/12 23:06, Bernd Paysan wrote:
[...]
If you have the incomplete repository, try a fossil pull, which then
will
fail with an error message.
Yep, you're right, that dies:
$ fossil pull -R out.fossil
Server:
On Fri, Oct 26, 2012 at 5:42 PM, Bernd Paysan bernd.pay...@gmx.de wrote:
We have managed to create a repository that can't be cloned anymore -
after
a fork and merge where some larger files have been changed (date
2012-09-26).
The two developers who created fork and merge were able to
Am Freitag, 26. Oktober 2012, 18:24:07 schrieb Richard Hipp:
On Fri, Oct 26, 2012 at 6:12 PM, David Given d...@cowlark.com wrote:
On 26/10/12 23:06, Bernd Paysan wrote:
[...]
If you have the incomplete repository, try a fossil pull, which then
will
fail with an error message.
Am Freitag, 26. Oktober 2012, 18:36:56 schrieb Richard Hipp:
If I clone from your repo, I do indeed get a corrupt clone. But if I
download the raw repo, set up a server locally (fossil server
vd-2012-03.fossil) then clone it locally (fossil clone
http://localhost:8080/ vd-new.fossil) the
Am Samstag, 27. Oktober 2012, 01:06:18 schrieb Bernd Paysan:
When I do this with my local fossil version, I get the same broken
repository.
I downloaded the current 1.24 release, and then, I can successfully clone it,
too. So I think you already have fixed the bug.
--
Bernd Paysan
If you
On Fri, Oct 26, 2012 at 7:13 PM, Bernd Paysan bernd.pay...@gmx.de wrote:
Am Samstag, 27. Oktober 2012, 01:06:18 schrieb Bernd Paysan:
When I do this with my local fossil version, I get the same broken
repository.
I downloaded the current 1.24 release, and then, I can successfully clone
12 matches
Mail list logo
