X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Envelope-From: paubert AT iram DOT es
Date: Mon, 31 Aug 2015 16:10:22 +0200
From: "Gabriel Paubert (paubert AT iram DOT es) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: "Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] Non-plated pin/via with copper annulus
Message-ID: <20150831141022.GB11756@visitor2.iram.es>
References: <CAGYR9vcipTvWXWUhxvdOSzOfuVhCxpNbcczeQF9nn4hr366G=Q AT mail DOT gmail DOT com>
 <20150831114226 DOT 13960 DOT qmail AT stuge DOT se>
 <CACwWb3D5eZQvYwC26ynN=DGLN_U_-jmxjezAPk0ekWfo-fs8sg AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACwWb3D5eZQvYwC26ynN=DGLN_U_-jmxjezAPk0ekWfo-fs8sg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Spamina-Bogosity: Unsure
X-Spamina-Spam-Score: -2.9 (--)
X-Spamina-Spam-Report: Content analysis details:   (-2.9 points)
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0017]
  0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
                             See
                             http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                              for more information.
                             [URIs: delorie.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

On Mon, Aug 31, 2015 at 02:29:29PM +0200, Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> What a hack. Oh well... Why not have a data structure that enables
> arbitrary padstacks?

Because padstacks should correspond to the same pin: here it's a jumper
between the top and bottom layer. Both pads are not necessarily
connected to the same net.

    Gabriel