X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-UW-Orig-Sender:	fpm AT homer03 DOT u DOT washington DOT edu
Date:	Fri, 12 Jun 2015 16:40:25 -0700 (PDT)
From:	"Frank Miles (fpm AT u DOT washington DOT edu)" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Parts with internally connected pins
In-Reply-To:	<B79C9937-FF0D-4301-9569-66E5EA167B03@till.com>
Message-ID:	<alpine.LRH.2.01.1506121638290.11317@homer03.u.washington.edu>
References:	<B79C9937-FF0D-4301-9569-66E5EA167B03 AT till DOT com>
User-Agent:	Alpine 2.01 (LRH 1217 2009-02-23)
MIME-Version:	1.0
X-PMX-Version:	6.1.0.2415318, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.6.12.233317
X-PMX-Server:	mxout24.cac.washington.edu
X-Uwash-Spam:	Gauge=X, Probability=10%, Report='
	TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_400_499 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, NO_URI_FOUND 0, REFERENCES 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __USER_AGENT 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 Fri, 12 Jun 2015, Donald Tillman wrote:

> What would be the best way to deal with parts that have pins that are internally connected together, and when laying out a board you can freely connect to one, or to the other, or both?  And do it in such a way that the pcb Optimize Rats Nest command doesn't complain.
>
[snip]

I usually make these 'unnecessary connections' on a dummy copper layer.

- Raw text -