X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 9 Jul 2015 16:06:15 +0200 (CEST) From: Roland Lutz To: geda-user AT delorie DOT com Subject: Re: [geda-user] Back annotation (was: developer excitement?) In-Reply-To: <44FED82A-8277-427B-87A8-FBC5E9A3D0E5@noqsi.com> Message-ID: References: <44FED82A-8277-427B-87A8-FBC5E9A3D0E5 AT noqsi DOT com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-360831950-1436450775=:1892" 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 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-360831950-1436450775=:1892 Content-Type: TEXT/PLAIN; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 9 Jul 2015, 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. > nearly all of the unnamed nets changed their names in this case A clever diff algorithm would have to compare connectivities independently of net names, so the remaining net name changes could easily be ignored. Roland --8323329-360831950-1436450775=:1892--