[fvwmorg/fvwm] c728fe: Updated colors to match website

Branch: refs/heads/default-config Home: https://github.com/fvwmorg/fvwm Commit: c728feb8e5ed90ec73c0f2fc253316c5c96d1449 https://github.com/fvwmorg/fvwm/commit/c728feb8e5ed90ec73c0f2fc253316c5c96d1449 Author: somiaj Date: 2016-10-24 (Mon, 24 Oct

[fvwmorg/fvwm] b153c8: New Icon

Branch: refs/heads/default-config Home: https://github.com/fvwmorg/fvwm Commit: b153c82fd2d91766cc43b9312e89b5a57d0b53ed https://github.com/fvwmorg/fvwm/commit/b153c82fd2d91766cc43b9312e89b5a57d0b53ed Author: somiaj Date: 2016-10-24 (Mon, 24 Oct

[fvwmorg/fvwm] feee40: Script to copy default config

Branch: refs/heads/default-config Home: https://github.com/fvwmorg/fvwm Commit: feee40e61f9bfd9f821a560573c56819eae1cdc7 https://github.com/fvwmorg/fvwm/commit/feee40e61f9bfd9f821a560573c56819eae1cdc7 Author: somiaj Date: 2016-10-24 (Mon, 24 Oct

Re: Excluding files from Travis-CI

On Tue, Oct 25, 2016 at 02:56:55AM +0100, Dominik Vogt wrote: > Is it possible to exclude commits that only touch files like > TODO.md or .gitignore from requiring a build before they can be > pushed to master? No. You can only do this on a per-branch basis in Travis-CI -- and even then, you

Excluding files from Travis-CI

Is it possible to exclude commits that only touch files like TODO.md or .gitignore from requiring a build before they can be pushed to master? Ciao Dominik ^_^ ^_^ -- Dominik Vogt

Re: [fvwmorg/fvwm] 0c5211: Expose: don't flush accumulated events

On Tue, Oct 25, 2016 at 01:59:46AM +0100, Thomas Adam wrote: > On Tue, Oct 25, 2016 at 01:42:58AM +0100, Thomas Adam wrote: > > On Tue, Oct 25, 2016 at 01:34:57AM +0100, Dominik Vogt wrote: > > > I fear this commit is too disruptive. Aggregating Expose events > > > is very important to deal with

[fvwmorg/fvwm] 40a6bb: TODO comments

Branch: refs/heads/master Home: https://github.com/fvwmorg/fvwm Commit: 40a6bb74c13873b5bb93759fd0b79efa939a5942 https://github.com/fvwmorg/fvwm/commit/40a6bb74c13873b5bb93759fd0b79efa939a5942 Author: Dominik Vogt Date: 2016-10-25 (Tue, 25 Oct 2016)

Re: Final long term stable version

On Tue, Oct 25, 2016 at 02:01:04AM +0100, Dominik Vogt wrote: > That leaves much room for interpretation. A "clean break" to me > would mean to write it from scratch, and that's practically > impossible because the fvwm2 window managing code contains many > hundreds of hours undocumented

[fvwmorg/fvwm] 40a6bb: TODO comments

Branch: refs/heads/dv/todo-comments Home: https://github.com/fvwmorg/fvwm Commit: 40a6bb74c13873b5bb93759fd0b79efa939a5942 https://github.com/fvwmorg/fvwm/commit/40a6bb74c13873b5bb93759fd0b79efa939a5942 Author: Dominik Vogt Date: 2016-10-25 (Tue, 25 Oct

Re: Final long term stable version

On Tue, Oct 25, 2016 at 01:38:17AM +0100, Thomas Adam wrote: > On Tue, Oct 25, 2016 at 01:08:21AM +0100, Dominik Vogt wrote: > > > I wouldn't bother with this point---fvwm3 should be a separate repository > > > entirely. > > > > Why? Unless some people step up and tell us they'd want to take > >

Re: [fvwmorg/fvwm] 0c5211: Expose: don't flush accumulated events

On Tue, Oct 25, 2016 at 01:42:58AM +0100, Thomas Adam wrote: > On Tue, Oct 25, 2016 at 01:34:57AM +0100, Dominik Vogt wrote: > > I fear this commit is too disruptive. Aggregating Expose events > > is very important to deal with race conditions cause by > > applications doing crazy stuff. Is

Re: [fvwmorg/fvwm] 0c5211: Expose: don't flush accumulated events

On Tue, Oct 25, 2016 at 01:34:57AM +0100, Dominik Vogt wrote: > I fear this commit is too disruptive. Aggregating Expose events > is very important to deal with race conditions cause by > applications doing crazy stuff. Is there some explanation of the > problem that was fixed with this commit?

Re: Final long term stable version

On Tue, Oct 25, 2016 at 01:08:21AM +0100, Dominik Vogt wrote: > > I wouldn't bother with this point---fvwm3 should be a separate repository > > entirely. > > Why? Unless some people step up and tell us they'd want to take > over fvwm2 development, what is the gain of duplicating all >

Re: [fvwmorg/fvwm] 8e9804: configure.ac: appease CLANG

On Mon, Oct 24, 2016 at 05:24:07PM -0700, GitHub wrote: > Branch: refs/heads/dv/stable-fvwm2 > Home: https://github.com/fvwmorg/fvwm > Commit: 8e9804aa79e6dcba040ab1e4cb6e6e56fae6c5e4 > > https://github.com/fvwmorg/fvwm/commit/8e9804aa79e6dcba040ab1e4cb6e6e56fae6c5e4 > Author:

Re: [fvwmorg/fvwm] 0c5211: Expose: don't flush accumulated events

On Sat, Aug 06, 2016 at 01:09:23AM -0700, GitHub wrote: > Branch: refs/heads/master > Home: https://github.com/fvwmorg/fvwm > Commit: 0c5211e20940cd8dc811753c83118107d6964c8c > > https://github.com/fvwmorg/fvwm/commit/0c5211e20940cd8dc811753c83118107d6964c8c > Author: Thomas Adam

Re: Final long term stable version

On Tue, Oct 25, 2016 at 01:08:21AM +0100, Dominik Vogt wrote: > On Tue, Oct 25, 2016 at 12:53:44AM +0100, Thomas Adam wrote: > > On Tue, Oct 25, 2016 at 12:48:01AM +0100, Dominik Vogt wrote: > > > Okay, then how about this: > > > > > > 1. Start a branch fvwm2-stable at 2.6.6 and document it as

[fvwmorg/fvwm] 8e9804: configure.ac: appease CLANG

Branch: refs/heads/dv/stable-fvwm2 Home: https://github.com/fvwmorg/fvwm Commit: 8e9804aa79e6dcba040ab1e4cb6e6e56fae6c5e4 https://github.com/fvwmorg/fvwm/commit/8e9804aa79e6dcba040ab1e4cb6e6e56fae6c5e4 Author: Thomas Adam Date: 2016-10-25 (Tue, 25 Oct 2016)

Re: Final long term stable version

On Tue, Oct 25, 2016 at 12:53:44AM +0100, Thomas Adam wrote: > On Tue, Oct 25, 2016 at 12:48:01AM +0100, Dominik Vogt wrote: > > Okay, then how about this: > > > > 1. Start a branch fvwm2-stable at 2.6.6 and document it as the > >long term stable branch. > > OK. > > > 2. Backport fixes and

Re: Need of a "devel" branch?

On Sun, Oct 23, 2016 at 12:23:45AM +0100, Thomas Adam wrote: > On Sat, Oct 22, 2016 at 11:41:54PM +0100, Dominik Vogt wrote: > > Unless we're doing lots of disruptive stuff I'd prefer to > > propagate completed patchsets into master early so they get more > > testing. > > Yup. Well, that's what

Re: [fvwmorg/fvwm] 64d424: DEVELOPERS: mention NEWS file

On Tue, Oct 25, 2016 at 12:27:40AM +0100, Thomas Adam wrote: > On Tue, Oct 25, 2016 at 12:23:54AM +0100, Dominik Vogt wrote: > > On Mon, Oct 24, 2016 at 11:54:00PM +0100, Thomas Adam wrote: > > > On Mon, Oct 24, 2016 at 10:29:30PM +0100, Dominik Vogt wrote: > > > > ... but in a separate commit

Re: Final long term stable version

On Mon, Oct 24, 2016 at 11:52:03PM +0100, Thomas Adam wrote: > On Mon, Oct 24, 2016 at 11:24:58PM +0100, Dominik Vogt wrote: > > How about a compromise: Leave the code in, but announce that > > these features are deprecated and will not be maintained anymore. > > So, if any people still use some

Re: [fvwmorg/fvwm] 64d424: DEVELOPERS: mention NEWS file

On Tue, Oct 25, 2016 at 12:23:54AM +0100, Dominik Vogt wrote: > On Mon, Oct 24, 2016 at 11:54:00PM +0100, Thomas Adam wrote: > > On Mon, Oct 24, 2016 at 10:29:30PM +0100, Dominik Vogt wrote: > > > ... but in a separate commit please. Patching the NEWS file in > > > the same commit as the code

Re: [fvwmorg/fvwm] 64d424: DEVELOPERS: mention NEWS file

On Mon, Oct 24, 2016 at 11:54:00PM +0100, Thomas Adam wrote: > On Mon, Oct 24, 2016 at 10:29:30PM +0100, Dominik Vogt wrote: > > ... but in a separate commit please. Patching the NEWS file in > > the same commit as the code change makes bug hunting and reverting > > patches more difficult. > >

Re: [fvwmorg/fvwm] 64d424: DEVELOPERS: mention NEWS file

On Mon, Oct 24, 2016 at 10:29:30PM +0100, Dominik Vogt wrote: > On Sun, Oct 23, 2016 at 02:46:46AM +0100, Dominik Vogt wrote: > > On Sat, Oct 22, 2016 at 06:32:12PM -0700, GitHub wrote: > > > Branch: refs/heads/ta/reluctant-news > > > Home: https://github.com/fvwmorg/fvwm > > > Commit:

Re: Final long term stable version

On Sun, Oct 23, 2016 at 11:50:48AM +0100, Thomas Adam wrote: > On Sun, Oct 23, 2016 at 11:46:23AM +0100, Dominik Vogt wrote: > > The old stable branch should provide important fixes for people > > who use old versions, and that includes not taking away stuff from > > them, no? The idea is that

Re: [fvwmorg/fvwm] acd886: Infostore: persist on restart

On Mon, Oct 24, 2016 at 03:02:11PM -0700, GitHub wrote: > Branch: refs/heads/dv/master-late-deletes Forget about what the commit mail says. This branch is an attempt to resort the patches after 2.6.6 so that the patches removing features come last. It mostly works out of the box, except for

[fvwmorg/fvwm] acd886: Infostore: persist on restart

Branch: refs/heads/dv/master-late-deletes Home: https://github.com/fvwmorg/fvwm Commit: acd8865c9962ba39cdf789e0a2ac6859a2ea5621 https://github.com/fvwmorg/fvwm/commit/acd8865c9962ba39cdf789e0a2ac6859a2ea5621 Author: Thomas Adam Date: 2016-10-24 (Mon, 24 Oct

Re: regression from 2.6.5 to 2.6.6 ?

On Mon, Oct 24, 2016 at 21:59 (+0100), Dominik Vogt wrote: > On Sun, Oct 23, 2016 at 11:39:14AM -0300, zli...@ns.sympatico.ca wrote: >> On Sun, Oct 23, 2016 at 13:25 (+0100), Dominik Vogt wrote: > ... >>> Can you please try out the branch "dv/fix-cr-merging" tha I've >>> just pushed and see if

[fvwmorg/fvwm] ca34f1: NEWS.

Branch: refs/heads/dv/fix-cr-merging Home: https://github.com/fvwmorg/fvwm Commit: ca34f1946003af35a16e36ad8bf4025303388948 https://github.com/fvwmorg/fvwm/commit/ca34f1946003af35a16e36ad8bf4025303388948 Author: Dominik Vogt Date: 2016-10-24 (Mon, 24 Oct

Re: [fvwmorg/fvwm] 64d424: DEVELOPERS: mention NEWS file

On Sun, Oct 23, 2016 at 02:46:46AM +0100, Dominik Vogt wrote: > On Sat, Oct 22, 2016 at 06:32:12PM -0700, GitHub wrote: > > Branch: refs/heads/ta/reluctant-news > > Home: https://github.com/fvwmorg/fvwm > > Commit: 64d4244746754610a64ed35de9ca69e557d3e25a > > > >

[fvwmorg/fvwm] b1ebfd: NEWS.

Branch: refs/heads/dv/fix-cr-merging Home: https://github.com/fvwmorg/fvwm Commit: b1ebfd89ab55807ee73c15483da90d74a5a949c8 https://github.com/fvwmorg/fvwm/commit/b1ebfd89ab55807ee73c15483da90d74a5a949c8 Author: Dominik Vogt Date: 2016-10-24 (Mon, 24 Oct

[fvwmorg/fvwm] fe2fd6: NEWS.

Branch: refs/heads/dv/fix-cr-merging Home: https://github.com/fvwmorg/fvwm Commit: fe2fd6ac9cca0e701cc3cb8b2e6adf3c4377d1c2 https://github.com/fvwmorg/fvwm/commit/fe2fd6ac9cca0e701cc3cb8b2e6adf3c4377d1c2 Author: Dominik Vogt Date: 2016-10-24 (Mon, 24 Oct

[fvwmorg/fvwm] 327cb9: NEWS.

Branch: refs/heads/dv/fix-cr-merging Home: https://github.com/fvwmorg/fvwm Commit: 327cb930f3d8a901b791ceb32c566d9a33519532 https://github.com/fvwmorg/fvwm/commit/327cb930f3d8a901b791ceb32c566d9a33519532 Author: Dominik Vogt Date: 2016-10-24 (Mon, 24 Oct

Re: regression from 2.6.5 to 2.6.6 ?

On Sun, Oct 23, 2016 at 11:39:14AM -0300, zli...@ns.sympatico.ca wrote: > On Sun, Oct 23, 2016 at 13:25 (+0100), Dominik Vogt wrote: ... > > Can you please try out the branch "dv/fix-cr-merging" tha I've > > just pushed and see if the fix works for you? (For me, it does.) > > And it does for me.

[fvwmorg/fvwm] d4258e: Fix sanitising XConfigureRequest and XConfigureNot...

Branch: refs/heads/dv/fix-cr-merging Home: https://github.com/fvwmorg/fvwm Commit: d4258ee0cc1ad70e15ac6dca9c6f98c52d66d033 https://github.com/fvwmorg/fvwm/commit/d4258ee0cc1ad70e15ac6dca9c6f98c52d66d033 Author: Dominik Vogt Date: 2016-10-24 (Mon, 24 Oct

[fvwmorg/fvwm] e7c39c: Add default-config to fvwm

Branch: refs/heads/default-config Home: https://github.com/fvwmorg/fvwm Commit: e7c39c6e73aebdb3ed7ee5f70bbdc823c89208a0 https://github.com/fvwmorg/fvwm/commit/e7c39c6e73aebdb3ed7ee5f70bbdc823c89208a0 Author: Thomas Adam Date: 2016-10-24 (Mon, 24 Oct 2016)