My use case is similar to what Adam describes. I already wrote a mail about
this some time ago, but as I was absent last month, I couldn’t look at this
feature in more detail until now. To reiterate, we use Fossil for collaborative
paper writing. There are a lot of supplementary data that is
Dear all,
I am serving repositories on our internal server via the Fossil GCI mechanism
behind Apache2 with SSL. The system is OS X. Everything was running perfectly,
but today I have updated the OS X Server app to the new version and while
everything is still running, Fossil now fails to
Ok, I have tried to track it down a little bit. I looked around in the code and
found the ‘debug’ option hidden within the CGI server. The binary crashes
because the cgi_parameter() is called with NULL from the
login_check_credentials(). This appears to happen because the
login_cookie_name()
Yep, this seems to work just fine.
Thanks!
From: Richard Hipp
I do not understand the underlying cause of your problem. But the latest
check-in might fix it.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Dear all,
I am hosting the Fossil repositories on our server via the CGI scripts (as
described in fossil documentation). Every repository has its own CGI script
(for cosmetic reasons).
When creating a new repository and subsequently trying to access it via CGI, I
get a crash in fossil. The
It shouldn't be crashing. But I don't have any idea what the problem is.
Which version of Fossil are you running? Can you recompile using -g so
that we get better information in the crash log?
This is the trunk [de17e35bf1] on OS X 10.10, using Apache/2.3.9
I am sure that the binary was
Dear all,
Fossil’s built-in merge works very well, but for our workflows (academic
writing), it would be very useful to merge all differences manually (i.e.,
every difference should be treated as a merge conflict). This allows the PIs to
keep a clear overview of all the changes and make sure
Thanks for the comments!
I will submit the Contributor’s Agreement ASAP. I was not aware that the
development list existed, and now that I have registered there, please feel
free to move the conversation to it. I am not very comfortable about mailing
lists because its not a tool I use a lot,
Dear all,
if I understand it correctly, when merging files fossil tries to use its own
algorithm (the src/merge3.c/blob_merge() function) as good as it can, and
attempts to fall back to an external merge tool (defined by gmerge-command) if
it is not happy with the result.
For our
Dear all,
I am currently looking into the possibility of using Fossil as our next SCM
(we currently use Mercurial, and while it works, many things could be
improved). The task is primarily
collaborative paper writing in a research institute, most authors are
non-programmers and thus want
Stephan, Matt,
thank you for your quick answers!
That depends on several factors, several of which another list member will
hopefully detail for us, but what i can say is if you clone like this:
fossil clone http://remoteUserName@server/... therepo.fsl
then pull/push will use that
I have found the problem - seems that the fossil version installed on my mac
was still 1.27 and the user name takeover has been added in 1.28.
Now it works like a charm and I am very happy!
Sorry for the noise and thanks again for the quick answers!
— Taras
On 04 Mar 2014, at 21:55 ,
12 matches
Mail list logo
