X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Wed, 16 Apr 2014 20:12:00 -0400
Message-Id: <201404170012.s3H0C0SU021800@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20140417000357.21967.qmail@stuge.se> (message from Peter Stuge
	on Thu, 17 Apr 2014 02:03:57 +0200)
Subject: Re: [geda-user] Freerouting finally free (GPL3)
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> <20140417000357 DOT 21967 DOT qmail AT stuge DOT se>
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


> 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.

How is creating and publishing a new repo elsewhere simplier than
using an existing repo?  Especially since Bert already has write privs
in geda-project's repo?

I understand that git (or any SCM) lets you make copies of repos all
over the internet, but just because you CAN do it doesn't always mean
you SHOULD do it.  It would be much easier to find all gEDA-related
development, for example, if it happened in the gEDA repository.