X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
Date:	Wed, 20 Jan 2016 16:41:07 -0500
Message-Id:	<201601202141.u0KLf7RJ000985@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	geda-user AT delorie DOT com
In-reply-to:
	<CAC4O8c9eSFkCKxMv0GkpvfZruwGXdrpHnidNjznpttu57ujgNg AT mail DOT gmail DOT com>
	(geda-user AT delorie DOT com)
Subject:	Re: [geda-user] cleaner version of fixes to file format plugin
References:	<CAC4O8c88EnAJ1H4YL4rj2O10ihZAz_NYDMSBAWEmdknMNu2b4A AT mail DOT gmail DOT com>
	<CAJXU7q8AtP=UOZrM1e+7Vmimc5kxOjyNrrGjqxcanRTjBWsVDA AT mail DOT gmail DOT com>
	<569BCA7F DOT 70903 AT prochac DOT sk>
	<569BCC77 DOT 60700 AT iee DOT org>
	<CAC4O8c9_kMdr+3xhe4-CZvUxPGzgqBrLN=Kn+WdGqGVcV1Nbnw AT mail DOT gmail DOT com>
	<201601172146 DOT u0HLkPnT008691 AT envy DOT delorie DOT com>
	<CAC4O8c8u_X54Ro2idbfBf8WToHg0tt2=BJ_irEHcZ7BVH6-_BQ AT mail DOT gmail DOT com>
	<201601191958 DOT u0JJwWro024659 AT envy DOT delorie DOT com>
	<CAC4O8c-YYbW5MFG-Na7wPd2YFAmDDOYFm+6QA7ayNAUpDG8jjQ AT mail DOT gmail DOT com>
	<201601200200 DOT u0K20RDb012759 AT envy DOT delorie DOT com>
	<569EEF3D DOT 4080307 AT iee DOT org> <CAC4O8c9eSFkCKxMv0GkpvfZruwGXdrpHnidNjznpttu57ujgNg AT mail DOT gmail DOT com>
Reply-To:	geda-user AT delorie DOT com

> The people using stuff this ancient are unlikely to want to upgrade
> pcb anyway.  As you've argued yourself in the past, for them to
> suffer all the old version would have to somehow magically
> disappear.  I don't want to assume this is just a setup to make
> going C99 impossible, but you can probably see how it might look
> that way.

You're missing the point.  You keep guessing what our user base should
be doing, and not asking our user base what they *are* doing.  I've
listed the things we need to know and the steps we need to take before
we can make an informed decision that we haven't made, and you keep
trying to justify the change based on guesses and suppositions.

So to reiterate in summary...

1. Find out what our user base *has*.  This may include potential user
   base (Windows, BSD).

2. Figure out what the side-effects of the change *will be*

3. *Decide* amongst ourselves to do it or not.

- Raw text -