Re: Separate or common project infrastructure fvwm v2/v3.

2016-10-27 Thread Ethan Raynor
, and is not done per branch. So that to me suggests you'll have to have a separate repo for fvwm-3 if you want to do releases - since Github does these per tag, not branch. HTH, Ethan Raynor

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

2016-11-13 Thread Ethan Raynor
Hi, Is it OK to request these sorts of conversations take place someplace else? I did not know before that there's a lot of heated conversations. I don't want to have to read these. Please be considerate. Or agree on something and move on, may be? Ethan On Sun, Nov 13, 2016 at 1:43 AM,

Re: fvwm3 repo (WAS: Re: Separate or common project infrastructure fvwm v2/v3.)

2016-11-13 Thread Ethan Raynor
is better. Thanks again though. Ethan On Mon, Nov 14, 2016 at 1:03 AM, Dominik Vogt <dominik.v...@gmx.de> wrote: > Please don't top post on the fvwm lists. > > On Mon, Nov 14, 2016 at 12:44:47AM +0000, Ethan Raynor wrote: >> it's those points i would like to see put elsewher

fvwm3 discussion continuing?

2016-11-01 Thread Ethan Raynor
Hey all, I've had a few mail probs recently and wondered if the discusion about fvwm3 is still happening? If it is- what are the outcomes from any conversations? Ethan