X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Scanned: amavisd-new at neurotica.com
X-NSA-prism-xkeyscore: I do not consent to surveillance, prick
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=neurotica.com;
	s=default; t=1436453237;
	bh=6lLM0J3DAYjKwt0j5ICPsDTZKURVJBlgFk65ABMD32c=;
	h=Date:From:To:Subject:References:In-Reply-To;
	b=bGur+hGaAkmAyYAB22YRv2DZmOiE3ZUQyq4oxHnjL6ScMTn8m2pJuwBBre2PArnjM
	 NliZSwr8OjF6nTOS/FlokcG4XTb6oEr3DU3WLL7lMcLS185+E7ndnHnSwCiPnet2cZ
	 bs1YZgR3x+Yt6WXndBl+jgfK/4ekBqjyYFfXRrdY=
Message-ID: <559E8975.9050805@neurotica.com>
Date: Thu, 09 Jul 2015 10:47:17 -0400
From: "Dave McGuire (mcguire AT neurotica DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Back annotation
References: <CAM2RGhTpfbqM7zNn72TBOjeL7B7LPT1PxSEU3+9aDdChFrPFTg AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1507090507530 DOT 6924 AT igor2priv> <alpine DOT DEB DOT 2 DOT 11 DOT 1507091329350 DOT 3444 AT nimbus> <alpine DOT DEB DOT 2 DOT 00 DOT 1507091404410 DOT 6924 AT igor2priv> <44FED82A-8277-427B-87A8-FBC5E9A3D0E5 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 11 DOT 1507091601150 DOT 1892 AT nimbus> <11988591-8CA7-4132-B14A-21A53895E63E AT noqsi DOT com>
In-Reply-To: <11988591-8CA7-4132-B14A-21A53895E63E@noqsi.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t69EnPZW025598
Reply-To: geda-user AT delorie DOT com

On 07/09/2015 10:25 AM, John Doty wrote:
>>> If you’re just making changes until a diff shows nothing, it doesn’t matter whether you make them upstream or downstream. Just quit when you have a match!
>>
>> This sounds reasonable to me.  So the common denominator is to load a "target netlist" into gschem and show the differences between the current state and the target state, either by highlighting them in the schematic or by showing a diff?  This shouldn't be too difficult to implement.
> 
> Not into gschem. Keep gschem clean, please. I just displayed a diff in a terminal window.

  Why are you assuming that adding this (or anything else!) will
automatically make gschem "dirty"?

  First, maybe such new functionality could be made a configure-time
option.  Second, and perhaps more intuitively...if you don't like a new
feature, don't use it.

               -Dave

-- 
Dave McGuire, AK4HZ
New Kensington, PA