On Wed, Apr 8, 2015 at 5:48 PM, wrote:
> I dislike JS as much as the next guy. However, I still feel that
> keeping the C simple makes the server cleaner and more auditable and the
> web UI more capable. I've only used Fossil for a week so far so take it
> for what it's worth, but it seems like
FWIW: The three Fossil self-hosting repositories stay in sync via a
cron job running on each server. See
https://www.fossil-scm.org/fossil/doc/trunk/www/selfhost.wiki for
additional information;.
On 4/8/15, Richard Hipp wrote:
> On 4/8/15, li...@ggp2.com wrote:
>> Is anyone interested in a dif
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 be
On Wed, Apr 8, 2015 at 5:24 PM, wrote:
> Thanks for the response, and sorry for bugging you :)
>
You're not bugging! i wish i could respond more fully to your posts, but my
left hand simply can't do it for the time being, and typing any notable
amount with only one hand is a real pain in the but
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 sort
On 4/8/15, li...@ggp2.com wrote:
> 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.
>
Th
On Wed, Apr 8, 2015 at 5:02 PM, wrote:
> 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
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 +, li.
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
(f
9 matches
Mail list logo
