X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Tue, 8 Dec 2015 14:12:06 -0500 Message-Id: <201512081912.tB8JC6Mb026336@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: <41B9CE53-BEB6-4982-BD0B-A4C024449FD6@noqsi.com> (message from John Doty on Tue, 8 Dec 2015 09:05:07 -1000) Subject: Re: [geda-user] gsch2pcb after refdes-renum? (If implemented syncronization detail) References: <56658683 DOT 401 AT envinsci DOT co DOT uk> <20151207153821 DOT c2ac19e6f24b1776a3595e4a AT gmail DOT com> <20151208091411 DOT c8968b0bedb705765529176c AT gmail DOT com> <201512081819 DOT tB8IJBrt022764 AT envy DOT delorie DOT com> <41B9CE53-BEB6-4982-BD0B-A4C024449FD6 AT noqsi DOT com> Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Part of software development discipline is saying *no* to desires > when the unintended consequences of their implementation will cause > serious trouble. And another part is seeing if someone else has already solved the problem, so that there aren't any unintended consequenses and no serious trouble. Which is why I asked. I'd rather help users solve their problems than put blinders on and ignore them, if there's a solution available.