On Wed, 23 Aug 2017 18:09:56 +0200, Richard Hipp <d...@sqlite.org> wrote:
more important: is a fix/work-around possible (apart from telling me to
do
it myself which I would have a hard time with ...)
Hold on there, honcho. We are not your employees. This is a community
effort. Expressing impatience with the debugging process is not an
effective strategy for recruiting volunteer helpers to work on the
problem.
I beg your pardon? you've got that completely wrong... by no means was
this intended to signal/express impatience on my side. I am *not*
impatient. and no need to explain the very obvious to me (regarding
community effort and you not being my employees...), really. I appreciate
the work invested into fossil as much as the next guy.
I was just asking whether a fix (or some user side work around I am not
aware of) is possible/available. nothing more, ok? and the parenthesis
just indicated that possibly proposing I contribute a patch would not be
realistic due to lack of expertise on my side in C programming... that's
all. hope this is straightened out now..
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
