t means, I would prefer to keep
this part as it is now by default. Sorry ;-(
Re-using the -v/--verbose option wouldn't be a good idea either,
as this options is used for displaying the modified files in addition.
That leaves implementing an additional option as the only
viable one, IMHO
x27;t make sense at all
Thanks, Taras, for your report!
(although docker images for fossil can be created now, it still
doesn't work 100% as I expect, still experimenting - trying to get
it right for Fossil 1.30 . )
Regards,
Jan Nijtmans
___
"fossil server" sets the server-code,
while the project-code is set by the first "fossil sync". Then we have
a kind of "virgin" template repository which takes the project-id of
the first repo it is syncing with .. but it's not trivial ...
Regards,
Jan
hat
it's worth it, maybe I implement it some day .. )
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
;
I think fossil should do the same in this case. That is a valid
request in my view.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
plicated, so line endings are no longer CR+LF, but instead
> CR+CR+LF ... which is ... a problem.
See:
<http://www.fossil-scm.org/index.html/info/f2fc37c063>
Thanks for your report!
Regards,
Jan Nijtmans
___
fossil-users mailing li
2014-11-26 11:13 GMT+01:00 Jan Nijtmans :
> See:
> <http://www.fossil-scm.org/index.html/info/f2fc37c063>
>
> Thanks for your report!
A related problem on win32:
C:\Users\me>fossil cat test/utf16be.txt
�� T h i s f i l e c o n t a i n s u t f - 1 6 b e t e x t .
to do executions in stead of the msys shell,
which has quite different quote handling. Better: use msys make.
I'm open to suggestions how to fix this.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
h
se files too. Could those become corrupt as well?
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
e use that in your cygwin environment.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
ith missing content
See also: close
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
2015-01-22 18:20 GMT+01:00 Sean Woods:
> Can the logic be updated so that it checks for WITH, in addition to
> SELECT, so that we/I can use CTEs?
<http://fossil-scm.org/index.html/info/ae72a652a7>
Thanks for the suggestion!
Regards,
e should be are gone. It's up to
you how to use that.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
t;http://www.fossil-scm.org/fossil/info/cfcd9b87dcf54a16>
Hope this helps.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
2015-01-29 11:05 GMT+01:00 Jan Nijtmans :
> When starting "fossil ui" locally and then opening the following URL:
>
> <http://localhost:8080/doc/ckout/www/changes.wiki>
>
> This page is not rendered correctly any more. With fossil
> 1.30 this still was OK. Bi
lease it.
My advise would be to abandon MinGW 4.0 (as their developers
did) and go back to 3.x, or switch to MinGW-w64.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
2015-02-22 16:17 GMT+01:00 Martin Gagnon :
> I don't know for msvc 2012, but it compile fine on MinGW.
> (with small warning that have to be fixed)
>
> Unfortunately I don't have access to a msvc 2012 compiler right now.
Should be fixed now. Thanks!
Regar
ch which has the "hidden" tag, this tag
has to be set explicitely.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
r("Expecting element with ID "+x);
>> else return e;}
> ^- Close curly brace
>>
>
> What am I overlooking?
Possible workaround (which is hardly more complicated) here:
<http://fossil-scm.org/index.html/info/e7ec49815b988811>
Regards,
ght "FileDescription" in the resource to
be used this way.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
ave as rm/mv do now.
Any objections against adding "fossil forget" as alias
to "fossil rm" If not, I'll be glad to add it, awaiting
further discussion.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
2015-03-06 16:58 GMT+01:00 Jan Danielsson :
> On 06/03/15 15:10, Jan Nijtmans wrote:
>> Any objections against adding "fossil forget" as alias
>> to "fossil rm" If not, I'll be glad to add it, awaiting
>> further discussion.
>
>No objec
2015-03-09 23:06 GMT+01:00 Tontyna :
> Hurray and thank you!
>
> Will `addremove` become `addforget`? (Sorry, couldn't resist nitpicking.)
It should be 'addforgetrename', with the added functionality that
renames are detected too .... ;-)
Fossil <1.30 had
bugs which ill-treat repositories without any commits. Those
were fixed in Fossil 1.30.
A workaround: If you really want to create the initial repository
with Fossil 1.30, use "fossil new --date-override now".
Regards,
Jan Nijtmans
___
invisible to the students).
Thanks to Tontyna for his excellent analysis, which made it
(at least to me) fully clear what really happend here.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
le repository by design :-)
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
ch isn't really there. The only problem
I see in your workflow is that you were not warned
that actually you were creating a fork, in 1.32 you
will get that warning (after doing the same steps):
$ fossil commit -m "commit b"
would fork. "update" first or use --allow
e.g. when multiple branches merge into the line which
> this op would want to back something out of.
Agreed. I don't think any simplification would be a good idea. Sorry!
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@
and 2
from the svn dump-load-format, version 3 is not yet implemented.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
script and catch this.
No, this is not expected. The n>0 check should have been n>1 here.
In Tcl 8.6:
$ tclsh8.6
% for {set i -} {$i<3} {set i [expr {$i+1}]} {puts $i\n};
-
can't use non-numeric string as operand of "+"
%
Thanks!
Jan Nijtman
quite
> cumbersome :)
Sounds like this bug in Tk, which is recently solved on trunk:
<http://core.tcl.tk/tk/info/0a4571b76a3e66c8>
In Tk 8.5.18/8.6.5 this should be fixed.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-us
out Tcl support, "fossil diff --tk" still works, it
just invokes "tclsh" to do the real work:
$ tclsh
% info patchlevel
8.6.4
%
(Current Tcl/Tk trunk is not renumbered to 8.6.5 yet, that normally
is done just before a new release)
Regard
ut
will do the right things at run-time.
Yes, this should be documented better..
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
function primary_parent_pid_from_rid() is not used anywhere.
I went ahead, so the fork detection for fossil update/status/info
(I din't hear anyone against that) will receive some more
wide-spread testing. I'll do more testing on the "sync-forkwarn".
Any more feedback welco
all where the fork is. Most people won't have any idea
why the warning was there, and what to do about it. I guess it will
only cause more confusion than that it helps people getting the
repository fork-free.
Maybe more valuable would be to adapt t
2015-04-14 21:11 GMT+02:00 Andy Bradford:
> Thus said Jan Nijtmans on Tue, 14 Apr 2015 16:36:18 +0200:
>> Maybe more valuable would be to adapt the /leaves page, so people
>> searching forks have an easy way to do so.
>
> I proposed this very thing a few days ago, an
tags: mistake)
(4) 2014-05-28 09:56:34 [7d445e593a9966] Moved to "mistake" because
this commit contains a typo causing a test to fail.
Was: Add an extra test to further verify that the FTS
notindexed option is working properly. (user: dan tag
h the UI)
So, a merge which merges the two tips of a fork together indeed closes
the fork. But
for other merges more needs to be done, that's how it functions (as it should).
Sorry ;-)
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
: Maybe the artifacts in a round-trip create
a fork, but this fork is resolved in some future round-trip which is still
part of the same sync operation.
It seems it's not wise at this moment to merge "sync-forkwarn" to trunk
since false warnings here may be more co
regression. If
> there is in fact a platform where you cannot include sys/ioctl.h if
> TIOCGWINSZ isn’t defined by termios.h, a different ifdef will be required.
It's very unlikely that a system having would not have
. I don't know a
uent discussion.
Work already has been done by Joe Mistachkin to resolve this (Thanks Joe!)
Just configure fossil using --with-legacy-mv-rm and then build it, then:
./fossil set mv-rm-files -global 1
I'm currently using fossil compiled this way, and so far it appears to
work
it isn't. Of course, I could explicitly add a "close" tag
here as workaround, but for the sake of bug reproducibility
I'll leave it like this ;-) Thanks! Good catch! Pleading guilty!
However, as you correctly stated, this is unrelated to the
recent fork handling improvements,
r on average in Fossil. We have had only 1 so far this year.
So, let's start testing:
<https://www.fossil-scm.org/index.html/info/560483f50436c9f7>
Keep good comments coming .!
Thanks!
Jan Nijtmans
___
fossil-users mailing list
2015-04-25 22:54 GMT+02:00 Richard Hipp :
> On 4/25/15, Jan Nijtmans wrote:
>> 2015-04-25 18:38 GMT+02:00 Andy Bradford:
>> So, let's start testing:
>> <https://www.fossil-scm.org/index.html/info/560483f50436c9f7>
>
> The "fossil forks" comm
th "fossil info" and use the more general
term "ambigeous branch" (of which "fork" is a special case)
<https://www.fossil-scm.org/index.html/info/4359bd8df2119799>
Regards,
Jan Nijtmans
___
fossil-users
a5c9994222f>
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--keep/"keep-glob" I am
aware of, at least, that's how I am using it.
- How about "fossil clean --verily --keep Makefile"? Despite the -keep
option, the Makefile will still be removed.
Regarding the other strengthening options, I agree!
Thanks!
Jan Nijtmans
he same: The
versioned setting content for those is even the same.
Thanks!
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
ose settings are convenient
in MY build environment, but they should not have beeen imposed
on others with different environments. I didn't realize that
at the time.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.or
means, you
probably don't need it but it won't hurt either)
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
SQLITE_ERROR: no such table: fmove
Thank you for your report. Should be fixed here:
<https://www.fossil-scm.org/index.html/info/89212c5a69576f77>
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.
ons. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I'll see if I can trace this somewhat further, but gdb's "bt" shows nothing :-(
Regards,
Jan Nijtmans
$ gdb ./fossil
2015-06-02 9:22 GMT+02:00 Jan Nijtmans :
> I'm seeing the same problem in /reports. See below. However,
> if I remove the -O2 compiler flag from the Makefile, everything
> works fine. So, this could be a gcc optimization bug.
It turns out not to be a gcc optimization bug
d803f9ad6>
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
.org/index.html/info/3ffb6a3e6299e92f>
(at least for this specific case, I'm sure there are more ...)
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
2015-06-03 17:42 GMT+02:00 Ron W :
> On Wed, Jun 3, 2015 at 10:24 AM, Jan Nijtmans
> wrote:
>>
>> 2015-04-25 1:29 GMT+02:00 Ron W :
>> > Would it be reasonable for Fossil to have a setting, or option in the
>> > diff/gdiff command setting, to indicate that re
if the current directory
is c:\Users\foo
(win32), /cygdrive/c/Users/foo (cygwin) or /c/Users/foo (msys).
See:
<http://www.fossil-scm.org/index.html/info/c9f3266836f1f7fe>
Thanks!
Jan Nijtmans
___
fossil-users mailing list
fossil-users@l
.2.8
> SSL (OpenSSL 1.0.2a 19 Mar 2015)
> UNICODE_COMMAND_LINE
This problem was fixed the very next day, 2015-05-29 17:14:59:
<http://fossil-scm.org/index.html/info/c56a387d47e5efde>
Regards,
Jan Nijtmans
___
fossil-users mailin
ourse,
Fedora and Ubuntu have the option to provide their own fossil binary,
which links with both libz and libssl dynamically. But such a
build will be Fedora/Ubuntu-specific, and is not guaranteed to
work on any other Linux distribution. I don't expect sqlite.org
to provide downloads for each
2015-05-25 11:34 GMT+02:00 Jan Nijtmans:
> For anyone interested, I built fossil 1.33 especially
> for win64, it's available here:
>
> <https://sourceforge.net/projects/cyqlite/files/fossil/>
>
> This binary is compiled with latest MinGW-w64 compiler,
> and wit
Or "file fossil"?
Is the fossil binary self-compiled or obtained elsewhere?
Is it a 32-bit or 64-bit binary, is it statically linked or not?
Answers to those questions might give a hint on what's happening here.
Regards,
Jan Nijtmans
__
sil:
<https://registry.hub.docker.com/u/nijtmans/fossil/>
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
lity to recover.
2) files > 10M (is this a good value?), those will be prompted for,
before removing them forever.
I never really needed that, therefore I didn't do enough with
it to thrust it for 100%. But if it's usefull to you, I'm happ
ome thoughts in writing. Will revisit
> when I have time.
Thanks for your idea, and having a look at the branch. It's
certainly not ready yet, but your input can get the
branch closer to being finalized.
Regards,
Jan Nijtmans
___
f
is part of the fossil code, just
wanted to let you know that I'm reading this with interest. As
soon as this problem is fixed, I would like to cherry-pick the
fix, and update the nijtmans/fossil docker image.
Regards,
Jan Nijtmans
___
fossil-users
t;abc.x" (a=all/y/N)? y
Yes, that's exactly how I expect it to work.
Thanks!
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
2015-07-10 12:04 GMT+02:00 Jan Nijtmans :
> $ ./fossil clean
> WARNING: Deletion of this file will not be undoable via the 'undo'
> command because the file is too big.
> Remove unmanaged file "abc.x" (a=all/y/N)? y
>
> Yes,
the problem is located and corrected.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
thing should be OK.
Then, enable it:
fossil set tcl 1
After that, it should work, but not in the test-th-eval command ;-)
You could try "fossil ui" and then go to Admin -> TH1. Typing
the command "tclEval {info tclversion}" from there w
l?
You should configure with "--with-tcl --with-tcl-stubs
--with-tcl-private-stubs".
This way (which should be the default IMHO) fossil will use its own
Tcl header for compilation (derived from Tcl 8.6.0), and check the
actual Tcl version at runtime which. This should still work with Tcl 8
4e to fossil.
It turns out that the cause of this problem is the following commit:
<http://www.fossil-scm.org/index.html/info/9431fec1ea098fea>
so I backed it out. My local trunk build doesn't show the problem
any more.
Regards,
Jan Nijtmans
2015-10-20 19:51 GMT+02:00 Joe Mistachkin :
> Jan Nijtmans wrote:
>>
>> It turns out that the cause of this problem is the following commit:
>> <http://www.fossil-scm.org/index.html/info/9431fec1ea098fea>
>> so I backed it out. My local trunk build doe
1-hooks --json --with-zlib
Just add the options --with-tcl-stubs and --with-tcl-private-stubs,
then it will work fine. (Don't ask me why this isn't the default
when using --with-tcl, I think it should be)
Regards,
Jan Nijtmans
___
fossil-us
i characters.
As far as I know, fossil doesn't use control characters to decide
the file is binary, only the null-byte. So I think something else
is triggering the binary detection. Too long lines, maybe?
Regards,
Jan Nijtmans
___
fossil-us
en the function
looks_like_binary() didn't exist yet. Should be fixed now:
<https://www.fossil-scm.org/fossil/info/b51ba29365b93b3f>
Whatever definition of BINARY is chosen, I think it should be
the same everywhere within fossil.
Thanks!
Jan Nijtmans
__
e MinGW-w64, then you
can use all unicode characters in the command line you like. See:
<http://fossil-scm.org/index.html/tktview/edab7bb5c973f41fced6>
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
h
2016-01-13 18:08 GMT+01:00 LM:
> Jan Nijtmans wrote:
>> However, I would recommend to use MinGW-w64, then you
>> can use all unicode characters in the command line you like
>
> A lot of die-hard original MinGW users including myself refuse to use
> MinGW-w64 due to lice
s in
> filenames), but maybe I'm missing something.
BROKEN_MINGW_CMDLINE is meant for the original mingw only, for
mingw-w64 everything's fine. For details, see:
<http://sourceforge.net/p/mingw/bugs/771/>
Regards,
Jan Nijtmans
___
only way I know which enables the use of _all_ unicode
characters on the command line, not only the ones in the current
windows code-page.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
an-glob setting
and related functionality altogether. It was a mistake.
For the reasons why, see:
<https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg11685.html>
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.
uld clean itself while running. It could also be used to protect
specific files which don't influence the build (such as long log files)
from being cleaned, those files will then typically be in
ignore-glob too. Not used very often, but still I prefer to keep it.
Rega
s your suggestion? Handle keep-glob in extras and
addremove just as in clean? I would support that, it doesn't
have to wait for fossil 2.0 if you would ask me. It would mean
that I can simplify my ignore-glob setting a bit, indeed
a bit more logical.
Regards,
Jan Nijtmans
___
;t do?
The difference can only be seen in verbose mode (-v). Any file
matching keep-glob will result in a warning:
KEPT file not removed (due to --keep or "keep-glob")
Agreed it's a very thin use-case, thinking about it now ;-)
Regards,
Jan Nijtmans
___
2016-06-10 2:01 GMT+02:00 Scott Robison:
> I just committed
> a one line fix (with multiple lines of comments to clarify what the code is
> doing in the tricky part).
Scott, I owe you. Many thanks! You are completely right, this was an
edge-case not covered for.
Regards,
Jan
2016-06-10 9:24 GMT+02:00 Scott Robison:
> On Fri, Jun 10, 2016 at 1:15 AM, Jan Nijtmans
> wrote:
>>
>> 2016-06-10 2:01 GMT+02:00 Scott Robison:
>> > I just committed
>> > a one line fix (with multiple lines of comments to clarify what the code
>> > i
est-failures but all failures turned out to be errors in the
expected test-outcome. I fixed those test-cases now, added more of
them, and fixed the invalid_utf8() function in trunk. Now all tests pass
with both trunk code and your code.
Many thanks, Scott ! Once more, fossil got bet
troduced with this commit:
<http://www.fossil-scm.org/index.html/info/f73411025e8ebec70029>
investigating ..
This appears to fix the bug, probably not the right fix . but it works.
<http://www.fossil-scm.org/index.html/info/a78e51185326b91f>
Rega
2016-07-05 16:18 GMT+02:00 Jan Nijtmans:
> But there is currently a bug in fossil which shows
> a closed fork with an additional arrow going up. Now I don't
> have an example any more showing this ;-(
Never mind ... found it:
<https://www.fossil-scm.org/index.html/info
401 - 488 of 488 matches
Mail list logo
