source, it was Ok. So
I suspect that the win32 binary was not a clean build. Maybe some local
debugging code was added which was never committed.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil
2012/10/19 Richard Hipp d...@sqlite.org:
It's been a couple of months since the last official release, so it seems
about time to do another. I propose to release the tip of trunk as version
1.24 on Monday. If anybody knows of a reason why this should not occur or
should be delayed, please
. If
it doesn't work, the binary will just behave as if Tcl is not installed,
nothing will crash. The Tcl stubs mechanism does't depend on compiler or
runtime, so if Tcl is compiled with a different compiler than fossil, it
still will work fine.
Regards,
Jan Nijtmans
can really judge that. The more people
try it and report their success (or not), the more likely
that it will go in eventually.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080
--user username here,
as it can be derived from the command-line already which
username is required
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo
,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
converter, not
in fossil itself. Quotes are not illegal in fossil, but the
backslash character is.
Proof:
$ fossil add str'i'ng.h
ADDED win/str'i'ng.h
$ fossil status
...
ADDED str'i'ng.h
See, no problem to add it at all.
Regards,
Jan Nijtmans
: string.h)
but apart from that everything could be made to work fine.
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
see a way to work around the two
remaining problematic characters.
I think this deserves a lot more testing. I will
Regards,
jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin
2012/11/22 Stefan Bellon sbel...@sbellon.de:
On Thu, 22 Nov, Jan Nijtmans wrote:
Stefan, could you try out [e6a1910fa8]?
This sounds very cool. :-)
However I still get:
$ ~/tmp/fossil addremove
[...]
/home/bellonsn/tmp/fossil: filename contains illegal characters: str\i\ng.h
...
Am I
are displayed unchanged.
- If more elaborate wiki markup is needed, it can always be
edited later in the UI.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman
2012/11/22 Michal Suchanek hramr...@gmail.com:
On 22 November 2012 14:35, Jan Nijtmans jan.nijtm...@gmail.com wrote:
I think I would fix that in the comment preprocessor.
The major disadvantage is, of course, that this ugly mess will be
likely visible in the command line view of the commits
2012/11/22 Jan Nijtmans jan.nijtm...@gmail.com:
2012/11/22 Stefan Bellon sbel...@sbellon.de:
On Thu, 22 Nov, Jan Nijtmans wrote:
Stefan, could you try out [e6a1910fa8]?
This sounds very cool. :-)
New test version in [d3bee356ba]. It changes the
filename contains illegal characters fatal
and rough patch is of some value.
Sure it is! I cannot test it now, but this is how I would expect
it to work.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman
2012/11/25 Jan Nijtmans jan.nijtm...@gmail.com:
2012/11/25 Stefan Bellon sbel...@sbellon.de:
Attached you'll find a patch that adds the unicode-glob to the
settings and respects its setting in the check-in. Additionally I
disabled all the check-in warnings (crnl, binary and unicode) in case
2012/11/25 Richard Hipp d...@sqlite.org:
2012/11/25 Jan Nijtmans jan.nijtm...@gmail.com:
Stefan, I committed your patch to the bellon-unicode branch.
Feedback welcome! At first sight, looks good to me.
Stefan, please fill out
http://www.fossil-scm.org/fossil/doc/trunk/www/copyright
2012/11/26 Stefan Bellon sbel...@sbellon.de:
On Mon, 26 Nov, Jan Nijtmans wrote:
Finally, I had a look at the bellon-unicode branch. I like the new
--no-warnings flag, being less dangerous as the --force flag.
The question is whether the naming of this new option is a good one
Agreed
2012/11/25 Jan Nijtmans jan.nijtm...@gmail.com:
New test version in [d3bee356ba]. It changes the
filename contains illegal characters fatal into
a warning, which should make your situation more
managable: Even though files containing '\' still
cannot be handled, they don't stop the
fossil
2012/11/30 Gilles gilles.gana...@free.fr:
1. BTW, if the MinGW version offers better support for shell use, why
is the Windows binary compiled with MSVC?
The Windows binary is compiled with MinGW, only the commandline
parser is replaced, in order to fix bugs like [13b7388964], [490b6c2edd]
, the mentioned utf-8 bugs were re-introduced.
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
'*'/'?'
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
2012/11/30 Jan Nijtmans jan.nijtm...@gmail.com:
Would switching the default build from MinGW to MinGW-w64
be an option?
I tested the command-line expansion feature from MinGW-w64.
It works! See [b1036fe5bf]. Should work on MSVC as well,
but still untested. Doesn't work on MinGW, because
.
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
mbcs-utf-8 conversion.
for other PREFIX values, use wmain and do unicode-utf-8 conversion.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil
2012/11/30 Richard Hipp d...@sqlite.org:
Can you suggest makefile changes to make this happen?
Done in [2459ee7b71]. Biggest advantage: the
parse_windows_command_line() is not necessary
any more.
Regards,
Jan Nijtmans
___
fossil-users mailing
the limitation that only characters from the current code-page
can be used. But when compiled with MinGW-w64, that limitation
doesn't exist any more: Any character can be used on the
commandline can be used, no matter what the code-page is.
I'll work out an example.
Regards,
Jan Nijtmans
express).
MinGW is lacking the -municode option, that's why
this cannot be fixed using MinGW.
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
.
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
of these characters in the path: \*[]?
Comment was not updated accordingly. Done now. Thanks!
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil
FYI,
The functions wcsnlen and wcsncpy_s are not used anywhere
in fossil code, they are only used within dirent.h.
Therefore, forwarded to Toni Rönkkö, for suggestions what
to do with it. Is it worth to fix it?
Regards,
Jan Nijtmans
-- Forwarded message --
From
for the complete list of Office 2007 mime-types and all possible extensions.
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
in the fossil web UI.
This would allow to enhance the file content checking such
that it detects invalid utf-8 as well, without the need to add a
new *-glob setting. The concept can be found in the
improve_commit_warning branch. Feedback appreciated.
Regards,
Jan Nijtmans
2013/1/21 Stefan Bellon sbel...@sbellon.de:
On Mon, 21 Jan, Jan Nijtmans wrote:
This patch is now in trunk already, but I'm just wondering if the
unicode-globwouldn't better be named encoding-glob. The
actual purpose of this warning is not whether some file
contains unicode, the fact
alternative.
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
2013/1/21 Stefan Bellon sbel...@sbellon.de:
On Mon, 21 Jan, Jan Nijtmans wrote:
I don't mind what the default is, as long as I can configure
it to give me the warnings. That's what the 3 *-glob
settings are providing.
Ok, then I misunderstood you when you reasoned with the web UI.
As long
Forwarded to the dirent.h maintainer.
Edward, from your other mails, I understand that you
are using Windows NT 4.0, which apparently lacks
the _set_errno() in its msvcrt??.dll. That explains
why this problem is not discovered before, not
many users are using Windows NT 4.0.
Regards,
Jan
2013/1/27 Edward Berner e...@bernerfam.com:
Hello,
When building with mingw32 (and without msys) using a command such as the
following:
mingw32-make -f win\Makefile.mingw USE_WINDOWS=1
The build fails when it tries to build zlib:
Thanks! Committed now.
Regards,
Jan Nijtmans
of this is not necessary, so I would expect a
#ifndef __WIN64 around the changed parts. This will also
make it easy to remove the code when no-one uses NT4 any more.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
fossil_strcmp in printf.c
Many Thanks!
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
2013/1/30 Stephan Beal sgb...@googlemail.com:
On Wed, Jan 30, 2013 at 11:10 AM, Jan Nijtmans jan.nijtm...@gmail.com
wrote:
Fossil's TCL support also appears to use dlopen()
- The link flag -ldl is missing on Linux. That's the shared library
containing dlopen,so - indeed - without it, Tcl
strcmp-fossil_strcmp everywhere,
but I don't think you want to do that in sqlite as well, therefore I came up
with the macro.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080
2013/1/30 Jan Nijtmans jan.nijtm...@gmail.com:
The $tclconfig(TCL_LIBS) contains the -ldl, but
$tclconfig(TCL_STUB_LIB_SPEC) does not, which is
OK. (the stub library doesn't use dlopen, fossil does)
Somehow, fossil should add -ldl here, such that the
--with-tcl-stubs option works
the user whether or not to
remember the password, as browsers typically do for their password
cache. (user: drh tags: trunk)
See:
https://www.fossil-scm.org/index.html/fdiff?v1=bc91379546130792v2=be285f713732c242
Fixed now.
Regards,
jan Nijtmans
it still should be disabled?
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
.
Regards,
Jan Nijtmans
Index: src/os_win.c
==
--- src/os_win.c
+++ src/os_win.c
@@ -4115,20 +4115,20 @@
** for converting the relative path name to an absolute
** one by prepending the data directory
should only be used on files, not directories. It looks like the $HOME
directory was the only directory this check was used on. So this should fix
the problem.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
the highest priority
of all flags, it should always be checked first by all
calling code. All other flags are meaningless whenever
LOOK_NUL is iset.
Any objections?
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil
of this mail), and the meaning
of the LOOK_SHORT flag:
#define LOOK_SHORT ((int)0x0100) /* Unable to perform full check. */
Wouldn't this flags always be 0 then?
I'm not in the position to make this decision.
Regards,
Jan Nijtmans
, not bytes.
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
for undeclared option --markdown
On Windows everything is OK.
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
the Rolling back... line?
That
should give a clue about what's really going on 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
in the
allowed
path length than later Windows versions.
You could checkout the repository on some short path like C:\foo.
Does that work?
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil
, and writes that
to the console. The 'bug' is in this conversion, but
if stdout is redirected this conversion doesn't take
place at all.
So, don't be fooled by this console output. When
automating this, everything should work OK.
Regards,
Jan Nijtmans
2013/4/8 Jan Nijtmans jan.nijtm...@gmail.com
There's also an option (5)
(5) Just automate it, doing nothing special.
If the consile output is redirected, no matter where to
(a file or a pipe), the output will be done as-is. When
not re-directed, the console code assumes
it is no
longer documented.
I also added many short options like -a for --all and -c for --closed
(JSON already had those) in places where it was missing.
If there are other suggestions or remarks for command-line
improvements, they are welcomed!
Regards,
Jan Nijtmans
2013/4/24 Edward Berner e...@bernerfam.com
On 4/23/2013 2:09 AM, Jan Nijtmans wrote:
If there are other suggestions or remarks for command-line
improvements, they are welcomed!
Well... I've noticed that some commands use --verbose and some use
--detail. Is that an accidental
-scm.org/index.html/info/c967b6619f. I
cannot find any problems with that.
Anyone? Did I miss anything?
Thanks!
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo
that a goldfish had THAT huge amount of memory.) ;-)
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
be called when the localdb is already open anyway), but it's safer
to leave it in: Maybe there is another location in fossil which I'm not
aware of where this rule is violated.
Thanks for your report!
Regards,
Jan Nijtmans
___
fossil-users
= in URL
parameters.
Another small step towards better consistancy. The original
options/parameters are
retained, so this should not break any existing scripts.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
: either remove
them without asking for confirmation (ignore-glob) or
keep them without asking for confirmation (keep-glob).
Any other ideas? Should fossil clean be undo-able like
fossil revert, or do we expect that people setting
ignore-glob know what they are doing?
Regards,
Jan
2013/5/3 Jan Nijtmans jan.nijtm...@gmail.com:
Any other ideas? Should fossil clean be undo-able like
fossil revert, or do we expect that people setting
ignore-glob know what they are doing?
Hm. I think an undo-able fossil clean is a good idea anyway
for such a dangerous command. And it's
2013/5/3 Richard Hipp d...@sqlite.org:
Or, perhaps there is a size limit (say 10MiB) above which cleaned files
are not undoable. Prompt for conformation prior to deleting an oversized
file that will not be undoable.
That sounds OK to me. To be continued.
Thanks!
Jan Nijtmans
/foo.o src/foo.h
$ fossil add src/foo.*
file src/foo.o should be ignored. Add it (a=all/y/N)? n
ADDED src/foo.c
ADDED src/foo.h
$ fossil add src/foo.* -f
ADDED src/foo.c
ADDED src/foo.h
ADDED src/foo.o
$
Feedback appreciated!
Regards,
Jan Nijtmans
2013/5/21 Alaric Snell-Pym:
I *love* it :-D
ABS
Thanks! As soon as my fossil clean proposal is evaluated, I'll rebase this
and put this up for evaluation as well.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users
integer expressions
Proposed patch (for SQLite), see below.
Regards,
Jan Nijtmans
Index: src/shell.c
==
--- src/shell.c
+++ src/shell.c
@@ -1562,15 +1562,15 @@
isNeg = 1;
zArg++;
}else if( zArg[0]=='+' ){
zArg
/clean should
be operated on. Without arguments, the operation stays
the same as it is now; it's fully upwards compatible.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin
Hi Stephan,
Just noted that JSON (CSON) on win32/64 cannot use 64-bit integers. My
attempt to fix this is in:
http://fossil-scm.org/index.html/info/50e8847df7
But becasue CSON is an amalgamation, I'm sure the real
fix should be somewhere else.
Regards,
Jan Nijtmans
this?
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
to 153
should be no problem for any compliant implementation. That's a lot
more than 132. !
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil
2013/6/20 Richard Hipp d...@sqlite.org:
Making this change will only introduce new, real bugs that impact everyday
users.
Thanks! That's OK with me. But then the question remains why the
return-type of db_last_insert_rowid() is not int then?
Regards,
Jan Nijtmans
for trouble!
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
$
Even if the files are missing locally, they are still in
the repository so they should be listed. Fixed now:
https://www.fossil-scm.org/index.html/info/c0b98195f9
(query borrowed from fossil delete/mv)
fossil changes and fossil status still to be done ;-)
Regards,
Jan Nijtmans
, but
for everyone else it will take much longer ;-)
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
2013/6/21 Stephan Beal sgb...@googlemail.com:
On Fri, Jun 21, 2013 at 3:57 PM, Richard Hipp d...@sqlite.org wrote:
I've already been working on the problem for 10 minutes.
Implemented fossil changes and fossil status now, which is much
simpler. It took me 25 minutes
Regards,
Jan
this:
$ fossil clean --ignore compat/\* -f
WARNING: KEPT file fossil.exe not removed
$ fossil clean --ignore compat/\* --keep -f
Removed ignored file: fossil.exe
Feedback appreciated! Any objections putting this in trunk?
Regards,
Jan Nijtmans
at least show something.
Thanks!
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
for format [-Wformat-extra-args]
make -C src/../compat/zlib PREFIX=x86_64-w64-mingw32- -f
win32/Makefile.gcc libz.a
Here is my proposed fix (actually, for sqlite 3.8.0)
Regards,
Jan Nijtmans
sqlite.patch
Description: Binary data
___
fossil-users
-
containing only a single character '*' - with your favorite
editor and commit it. Then everyone else who checks out
your repository can benefit from it too.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
it already in the sqlite sources
(Thanks!), so it's irrelevant now.
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
,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
2013/7/4 Jan Nijtmans jan.nijtm...@gmail.com:
Well, when I did this commit:
http://core.tcl.tk/itcl/info/0805477fbf
what I did was a fossil commit . while the current directory
was generic. So, why was Makefile.in committed then?
Found the bug:
http://www.fossil-scm.org/index.html
in the commit process there will be a panic anyway
when expected files are missing. The commit will be
rolled back then.
No way that Richard could have figured out all situations
in 5 minutes, not even 3 ;-)
Regards,
Jan Nijtmans
___
fossil
does that sound?
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
is the actual closing of the branch, but
everything else should be there ;-)
A nice thing is that if you decide not to commit the change, the
integrated branch is never closed. You can do a fossil undo
or fossil revert and everything is gone.
Regards,
Jan Nijtmans
think i just went from glass half full to glass half empty on this
topic :/.
Well, just try out the merge-integrate branch. I would say
the glass is full again.;-)
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil
:)
A similar think is already in development now, See:
https://www.fossil-scm.org/index.html/timeline?r=tkt-change-hook
It is meant for Ticket and Commit hooks, but more hooks
could be added the same way.
Regards,
Jan Nijtmans
___
fossil-users
=x86_64-w64-mingw32-
Then you get a WIN64 version of fossil.exe which
works in any environment (Cygwin32, Cygwin64, Msys, CMD),
and is super fast.
All Cygwin64 and Cygwin32 dll's have the same name, so you
cannot mix executables from those two environments.
Regards,
Jan Nijtmans
:\Windows directory! Cygwin clears
the Windows environment space, therefore none of the environment
variables can be found.
Proposed solution here (should move to sqlite if accepted):
http://www.fossil-scm.org/index.html/info/fec3c7fe3a
Regards,
Jan Nijtmans
it is. Unfortunately!
I'm trying to find out what the minimum patch is to get the Cygwin build
of fossil (both 32-bit and 64-bit) working again, so fossil can be
built out-of-the box on Cygwin again. Of course, any feedback
is welcome.
Regards,
Jan Nijtmans
style, so it will need some more work.
Regards,
Jan Nijtmans
sqlite3-3.7.17-3.src.patch
Description: Binary data
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
be a logical step.
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
2013/7/12 Stephan Beal sgb...@googlemail.com:
On Fri, Jul 12, 2013 at 10:25 AM, Jan Nijtmans wrote:
Well, just try out the merge-integrate branch. I would say
the glass is full again.;-)
Indeed it is! i like what you've done :)
I made one additional change: adding states
, just
keeping some room for future improvements. -3
is just as good.
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
to
determine which branches should be closed. Existing merges
never produce id=-4 so the query will give the empty result then.
Regards,
Jan Nijtmans
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080
the
--integrate option, the vmerge table is where this information
can be found.
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
the timeline doesn't display Closed Leaf for
[53ce8d2863], I would expect it to be there indicating that this
fork no longer can be committed to. Looks like a (minor) bug
to me.
Thanks!
Jan Nijtmans
___
fossil-users mailing list
fossil-users
2013/8/2 Jan Nijtmans jan.nijtm...@gmail.com:
2013/8/2 Andy Bradford
amb-sendok-1377995615.lfipjljlncecmjghe...@bradfords.org:
Does this mean that the merged fork is no longer a leaf at all? If this
is the case, why assign a closed tag to it?
...
Using --integrate makes it impossible
2013/8/2 Jan Nijtmans jan.nijtm...@gmail.com:
If the merged is not a leaf anymore, due to the commit itself, I
would expect this function to protect from adding a closed tag
(even though it doesn't really harm here).
Hm.
Bug fixed here: http://www.fossil-scm.org/index.html/info
your findings.
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
1 - 100 of 428 matches
Mail list logo
