Thomas Adam wrote:
> For those of you who follow fvwm-workers@ may already know some of this, but
> for those of you who don't, it's worth mentioning what the state of fvwm
> development holds for the future.
I am a long time fvwm user, and I have not touched my ".fvwmrc" in years
because it just
Hello all,
For those of you who follow fvwm-workers@ may already know some of this, but
for those of you who don't, it's worth mentioning what the state of fvwm
development holds for the future.
We have been discussing a lot about how we're able to make changes to fvwm
without breaking it for eve
Branch: refs/heads/master
Home: https://github.com/fvwmorg/fvwm
Commit: e8ab7a826310e1468545dbc07fc41d470347a805
https://github.com/fvwmorg/fvwm/commit/e8ab7a826310e1468545dbc07fc41d470347a805
Author: Thomas Adam
Date: 2016-11-11 (Fri, 11 Nov 2016)
Changed paths:
M READ
Branch: refs/heads/ta/docs
Home: https://github.com/fvwmorg/fvwm
Commit: e8ab7a826310e1468545dbc07fc41d470347a805
https://github.com/fvwmorg/fvwm/commit/e8ab7a826310e1468545dbc07fc41d470347a805
Author: Thomas Adam
Date: 2016-11-11 (Fri, 11 Nov 2016)
Changed paths:
M REA
On Fri, Nov 11, 2016 at 11:35:42AM +, Thomas Adam wrote:
> On Wed, Nov 09, 2016 at 09:01:20PM +, Thomas Adam wrote:
> > On Tue, Oct 25, 2016 at 01:26:19AM +0100, Dominik Vogt wrote:
> > > The branch dv/stable-fvwm2 is up for review. Collecting the
> > > patches was a piece of cake. Just o
On Wed, Nov 09, 2016 at 09:01:20PM +, Thomas Adam wrote:
> On Tue, Oct 25, 2016 at 01:26:19AM +0100, Dominik Vogt wrote:
> > The branch dv/stable-fvwm2 is up for review. Collecting the
> > patches was a piece of cake. Just one conflict with the NEWS
> > file. The branch builds fine for me, w
Branch: refs/heads/fvwm2-stable
Home: https://github.com/fvwmorg/fvwm
