X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=PSsCepCx1pLC9pGMqqpjdFctyx2Y2/83ufWH8avTZXk=;
	b=UwyBemul2YVforjYrx9qSorGsMr6zcpifBTbgMbRZwv8ahDmuJ96+gkpuRDZFDpjYh
	QQrLzlpMgQVNoFJiw0yjU6Bcyy5r+wLFCS7Gr+A+EBRXHf0m9DHDwhH96plaXzaMEGS7
	gv6k9YKypGQ0oBdPcQvOzO4sT6XSY75HxbFLaEg7kTqnd500YOJsrrn3FOhNRMTW8AS0
	tZSh4gKOqQH1SVrP+tb7vU/mZimBa3NhTFQDSxgds+R83dALceajZAaACxxELXY9vVHP
	tHDyXR8C0YJgog/3aWxJ9gAcSQ4sr9HTL4AeNmaEaV9s35NQ9JlhkAC3Bu2KxUpe96/j
	OK0w==
MIME-Version:	1.0
X-Received:	by 10.60.134.104 with SMTP id pj8mr17308932oeb.1.1450914104344;
	Wed, 23 Dec 2015 15:41:44 -0800 (PST)
In-Reply-To:	<E152C93E-7BFE-4E35-80DB-35454EFDDB21@noqsi.com>
References:	<CAJXU7q9ToaWE+wVJcF76yqHhjYZc5j95VL64cXPey-x4s_j9OA AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1512221634081 DOT 9035 AT igor2priv>
	<CAJXU7q_oFvUsdQ4zB+9Kp31dhOQPZa7b21AMZ9g_=VpYN1gAnw AT mail DOT gmail DOT com>
	<B7FF4997-34E5-4E61-AD74-28BE54E45801 AT noqsi DOT com>
	<CAJXU7q9SO+beJYXCdP4iubBnXu7WP1TrqcbJwvRtYz-2YgFQvw AT mail DOT gmail DOT com>
	<n5dgdv$g5t$1 AT ger DOT gmane DOT org>
	<CAHUm0tPZD-BLh1C4oYbYyE7cz-3JGjTk1SVtacugRYtcQm1k0w AT mail DOT gmail DOT com>
	<E152C93E-7BFE-4E35-80DB-35454EFDDB21 AT noqsi DOT com>
Date:	Thu, 24 Dec 2015 10:11:44 +1030
Message-ID:	<CAHUm0tOCEyO6kOQeTq8WnOZTMpqCFVozMLdMrUYMXqFsK_ebwA@mail.gmail.com>
Subject:	Re: [geda-user] Cross project collaboration on data models
From:	"Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user <geda-user AT delorie DOT 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

--047d7b471e00ca079005279943c8
Content-Type: text/plain; charset=UTF-8

Fair points re: the pin types being device family specific. At this stage
my utility allocates "passive" pin types for those which lack a direct
equivalent.

Although the lack of equivalent pin types won't cripple a workflow, it is
one extra barrier to pooling the collective work output of other FOSS eda
users who have already done the work and are sharing it.

Cheers,
Erich.

--047d7b471e00ca079005279943c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Fair points re: the pin types being device =
family specific. At this stage my utility allocates &quot;passive&quot; pin=
 types for those which lack a direct equivalent.<br><br></div>Although the =
lack of equivalent pin types won&#39;t cripple a workflow, it is one extra =
barrier to pooling the collective work output of other FOSS eda users who h=
ave already done the work and are sharing it.<br><br></div>Cheers,<br></div=
>Erich.<br></div>

--047d7b471e00ca079005279943c8--

- Raw text -