X-Authentication-Warning:	delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient:	geda-help AT delorie DOT com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-originating-ip:in-reply-to:references:date
	:message-id:subject:from:to:content-type:x-gm-message-state;
	bh=Rw5/aUkJNwraxgTbZEP3uBHIi7ficUelk47EOwS4bVs=;
	b=A7kICri0hcfzctU01I3NwnEiSsjl5jXBN3LBjGsJftIsicvv5FbMgijmsjB4IcGN+3
	c8dIfEWnqTUEVgsQdv5veHNghMrayjAQRZrwunBRr1oN/7UviKdaOFrsHZCU9iRaliMP
	EZOl7MotE0+K8Lqb7F7aJCRD8BMeDXlx7IIUmkTJXNwA3gnc+wTYUJUuQ7SzweQWiuKH
	Cde1ZYeNB4oWcgzNdO1+bomvRr1+Hz1NUxMlA+gnRPnvxdS0j2/QLM+oEwu9JJRN7T8Y
	+1chntKMW7jxeT7hpqKH8ql1b6Cx+ahSaShBSpToGUzjY72Kft55M+0NtIpdqDfOXMiK
	11SQ==
MIME-Version:	1.0
X-Originating-IP:	[50.72.201.196]
In-Reply-To:	<20121013174902.160C98117B42@turkos.aspodata.se>
References:	<alpine DOT BSO DOT 2 DOT 00 DOT 1210110132340 DOT 24638 AT wolfman DOT devio DOT us>
	<1349966191 DOT 2412 DOT 33 DOT camel AT AMD64X2 DOT fritz DOT box>
	<alpine DOT BSO DOT 2 DOT 00 DOT 1210112245150 DOT 13854 AT wolfman DOT devio DOT us>
	<20121012100446 DOT 93D648096B1E AT turkos DOT aspodata DOT se>
	<alpine DOT BSO DOT 2 DOT 00 DOT 1210122243220 DOT 2692 AT wolfman DOT devio DOT us>
	<20121013174902 DOT 160C98117B42 AT turkos DOT aspodata DOT se>
Date:	Sun, 14 Oct 2012 15:27:15 -0500
Message-ID:	<CA+DWcQacCk-QG03iwsZJUXvTumXc+FnHvzZeXf5PjNAgph2hiw@mail.gmail.com>
Subject:	Re: [geda-help] Adding new gschem symbols?
From:	Benjamin Bergman <ben AT benbergman DOT ca>
To:	geda-help AT delorie DOT com
X-Gm-Message-State:	ALoCoQldEoMsrr1PeVqTqeQINfCO9Lxh4NbiPyzzptU+ehOePhvb805GowxT5TZ5rFbkBRsV4wdZ
Reply-To:	geda-help AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-help AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--e89a8fb201da21851c04cc0abf03
Content-Type: text/plain; charset=ISO-8859-1

On Oct 13, 2012 12:50 PM, "Karl Hammar" <karl AT aspodata DOT se> wrote:
> Well you could possible use the md5sum of the sym file, what about:
>
> $ md5sum git/openhw/share/gschem/diode.sym
> cc2da042b5ea5afd65f4153bfff79b92  git/openhw/share/gschem/diode.sym
>
> And in the .sch file, this file is referenced by:
>
> C 18600 19900 1 0 0 diode.sym md5=cc2da042b5ea5afd65f4153bfff79b92

I think this is the way to go. This is essentially how all content is
tracked and referenced in git and adds a layer of corruption detection,
while costing very little in terms of resources or infrastructure.

--e89a8fb201da21851c04cc0abf03
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On Oct 13, 2012 12:50 PM, &quot;Karl Hammar&quot; &lt;<a href=3D"mailto:kar=
l AT aspodata DOT se">karl AT aspodata DOT se</a>&gt; wrote:<br>
&gt; Well you could possible use the md5sum of the sym file, what about:<br=
>
&gt;<br>
&gt; $ md5sum git/openhw/share/gschem/diode.sym<br>
&gt; cc2da042b5ea5afd65f4153bfff79b92 =A0git/openhw/share/gschem/diode.sym<=
br>
&gt;<br>
&gt; And in the .sch file, this file is referenced by:<br>
&gt;<br>
&gt; C 18600 19900 1 0 0 diode.sym md5=3Dcc2da042b5ea5afd65f4153bfff79b92</=
p>
<p dir=3D"ltr">I think this is the way to go. This is essentially how all c=
ontent is tracked and referenced in git and adds a layer of corruption dete=
ction, while costing very little in terms of resources or infrastructure.<b=
r>

</p>

--e89a8fb201da21851c04cc0abf03--

- Raw text -