Re: FVWM code moved to Github

Hi Jason, On 21 Mar 2016 17:04, "Jason L Tibbitts III" wrote: > I can continue to provide mailing lists in case people still find them > useful. Please. We really need those as they're a core part of our infrastructure. Is there some means by which you'd be able to delegate

Re: FVWM code moved to Github

Hi Jason, On 21 Mar 2016 17:18, "Jason L Tibbitts III" wrote: > > > "TA" == Thomas Adam writes: > > TA> Yes, and he's not always around, alas. > > I'm _almost_ always around. But I was in New Orleans with crappy > Internet, and got home to no Internet at

Re: FVWM code moved to Github

> "TA" == Thomas Adam writes: TA> Yes, and he's not always around, alas. I'm _almost_ always around. But I was in New Orleans with crappy Internet, and got home to no Internet at all. (Thanks, Comcast.) And I will be jaunting around Europe for most of July and some of

Re: FVWM code moved to Github

> "TA" == Thomas Adam writes: TA> I appreciate I've swooped in here, and just done this, but the TA> discussion[0] happened once before, and given the recent TA> circumstances with the borked CVS repository, it seemed unfair to TA> leave an impending release hanging. Just

FVWM website: WAS: [Re: FVWM code moved to Github]

On Sun, Mar 20, 2016 at 08:16:13PM -0400, Dan Espen wrote: > Moving the Fvwm-web source to Github won't help if we still need to > publish using Jason's services. So I've taken a look at this, and have noted the following: * PHP is used to regenerate the theming components of the site; * PHP is