X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <537BBBF5.3040800@xs4all.nl>
Date: Tue, 20 May 2014 22:32:53 +0200
From: Bert Timmerman <bert DOT timmerman AT xs4all DOT nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] DSN export
References: <CAHeNMgRs-b18a5xksiHdhUVUgH=ksFnBNq2m2+k-dTztr+5=GQ AT mail DOT gmail DOT com>	<537795BB DOT 2050604 AT xs4all DOT nl> <CAHeNMgS2sF0Yr9HpfZ30vGLNS3N7uwhermLACiDqV0TBhHXPvA AT mail DOT gmail DOT com>
In-Reply-To: <CAHeNMgS2sF0Yr9HpfZ30vGLNS3N7uwhermLACiDqV0TBhHXPvA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by XS4ALL Virus Scanner
Reply-To: geda-user AT delorie DOT com

Nathan Stewart wrote:
>
> I saw the branches, but no DSN related checkins going back to your 
> comments on the list circa 2011. Maybe I dont understand git 
> branching, and didnt have the code I thought I was looking at. Is this 
> in the main repo?(if not, I wouldnt expect to see the
>
Hi Nathan,

Basically the branching model of pcb development could have looked like 
this:

http://nvie.com/posts/a-successful-git-branching-model

The main differences are that the "develop" branch is identical with the 
"master" branch (still no stable major and minor versions), and that 
"hotfix" branches and commits live either in "master" or in the "release 
branches".

This branching model is explained more in detail here:

http://git-scm.com/book/en/Git-Branching

and if you want to read more you can do a google on "git workflow" or 
"git branching model".

For getting the DSN code available after cloning of pcb (see: 
http://pcb.geda-project.org/ and Installing from Source), one should do 
a "git checkout -b LP699471 origin/LP699471" or "git checkout -b 
LP699471rev1 origin/LP699471rev1", followed by the standard 
"./configure; make; make install" commands.


Another this is that AFAICT there is virtually no feedback from users 
(or devs) who tested? the code in these topic brances and gave a 
response for a merge to go.

Maybe pcb is just being used for production work and not for tinkering ;-)

If you encounter any problems with checking out or using the code please 
let me know.

Kind regards,

Bert Timmerman.