delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2017/02/12/14:06:12

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Sun, 12 Feb 2017 20:04:11 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] #pragma backannot
In-Reply-To: <alpine.DEB.2.11.1702121645300.11516@nimbus>
Message-ID: <alpine.DEB.2.11.1702122004040.29681@nimbus>
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1702121430580 DOT 7286 AT igor2priv> <alpine DOT DEB DOT 2 DOT 11 DOT 1702121645300 DOT 11516 AT nimbus>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
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

On Sun, 12 Feb 2017, Roland Lutz wrote:
> On Sun, 12 Feb 2017, gedau AT igor2 DOT repo DOT hu wrote:
>> I am not pushing it because I'd need it for pcb-rnd. I already have a 
>> gaf "fork: with fully working back annot for myself and for those who 
>> want to use the feature, so honestly, as an user or developer I don't 
>> really care if it makes it into any of the other "forks".
>
> To make it more visible, I added your code to the geda-gaf repository as 
> the branch home/rlutz/igor2-ba.
>
> After a first look at it, I think the code would need some cleanup, but 
> I don't see a fundamental reason why it shouldn't be merged into 
> geda-gaf. I wouldn't be comfortable deciding this on my own, though.

Ok, I now cleaned up the build system stuff, fixed two bugs and the 
compiler warnings, rebased it to what appears to be the last common commit 
shared with Vladimir's code and pushed it as home/rlutz/back-annotation.

I can't give the code a proper review, though, because I don't understand 
the gschem code (especially the text search) well enough.

I'm not sure how to proceed from here.  Is anyone familiar with the gschem 
internals willing to have a look at the code?  Or should I just merge it? 
The commit history doesn't appear to be very useful; should I squash it 
into one commit?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019