X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <20140417000357.21967.qmail@stuge.se>
Date: Thu, 17 Apr 2014 02:03:57 +0200
From: Peter Stuge <peter AT stuge DOT se>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Freerouting finally free (GPL3)
Mail-Followup-To: geda-user AT delorie DOT com
References: <1395878918 DOT 2126 DOT 7 DOT camel AT AMD64X2 DOT fritz DOT box> <53477BD5 DOT 3070001 AT xs4all DOT nl> <1397238146 DOT 861 DOT 11 DOT camel AT AMD64X2 DOT fritz DOT box> <201404111621 DOT 02147 DOT ad252 AT freeelectron DOT net> <534BED69 DOT 4050703 AT estechnical DOT co DOT uk> <534C1B44 DOT 20401 AT xs4all DOT nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534C1B44.20401@xs4all.nl>
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

Bert Timmerman wrote:
> Best course of action I can imagine is to set up a development branch 
> called "freerouting" or "devel" on http://git.geda-project.org/pcb/ and 
> start adding code and (hopefully) applying (Launchpad) patches later on.

It's even simpler than that, thanks to git.

> git://git.geda-project.org/pcb.git

Just clone this, write the code, and then publish it somewhere.

Start publishing commits long before you are finished writing code,
otherwise you are most likely going to write unacceptable code, which
is an unneccessary waste of time for everyone.

Publishing can be done in many ways. If you have no access to hosting
then you can always send your patches to a mailing list using the
git send-email command, or upload them to launchpad.


//Peter