I have not looked at the source yet, but I think your explanation gives
me a clear picture of the issues this would involve. This would need
some sort of polling/persistent connection, and I'm not sure how well
that meshes with Fossil's current web implementation.
This is somewhat OT, but I've
On Wed, Apr 08, 2015 at 05:15:10PM +0200, Stephan Beal wrote:
i'm (still) on medical leave with a disabled hand, so won't say more than:
there are a couple old posts in the list archives explaining various
pitfalls involved with autosync of ticket changes. Short form: it
introduces all sorts
Is anyone interested in a diff with this functionality? I don't mind
digging into the code, but I don't want to waste my time if it goes
against a core idea of Fossil. I'd just like the option of using it
with nothing external-facing other than SSH.
On Sat, Apr 04, 2015 at 03:07:41PM +,
Hello all!
I'm currently using fossil in a way which I think is somewhat
nonstandard, but had a feature request that could potentially be useful
to others as well.
Rather than having a central, pseudo-public facing process, we are using
fossil exclusively behind SSH. There is a shared account
On 2012-08-09 17:04, Chad Perrin wrote:
On Wed, Aug 08, 2012 at 08:10:58AM -0400, Richard Hipp wrote:
Fossil version 1.23 is now available on the website. See
http://www.fossil-scm.org/download.html
for additional information. Please report any problems to this mailing
list.
The
I'm a new user of fossil, having come grudgingly from CVS. Needless to say, my
stubbornness was unfounded-life is immeasurably easier than it was on CVS for
hundreds of little (and big) reasons.
In trying to convert my workflow to fossil, I haven't been able to find any
information in the wiki
6 matches
Mail list logo
