X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com 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=UlKY1U5BQfl+CxqIXW7A8DY+M2LxLVdBL34ub0Nd4pM=; b=rK0KXYZXNiP6G2hZhWhMltsEZaN5rO55nSrmJ9dOQhDNwYtDuNREo2JrnfasEqdP7P CYXrF3GKdv3xxe18jEhC46jV9fl2Xl0gL/WrRjaLm1Azxp5Dstm6w8qLX0k9NCbCIdn9 /6Fvq0wE2dgGdFqYXmDeOrBnjPjh2ssj5q5oN5y0u+eJZGZwes7BQEw5oS/tvM6q8JPy JXYmvOC/LhBsaijpiy8rI5kTDiqAAILU6PPOYtweqteZtBAy+FAGlCY1Sf0y+vsyuhJ/ 9JvNy7oYgfKluzbkOGaW7SyWdnQmD8pm01OkDANxT9rhcHBlu882CXErJsX2ujmsoCe3 Kniw== MIME-Version: 1.0 In-Reply-To: References: <1511E63C-F435-44B1-9734-C7AF7AF49A92 AT sbcglobal DOT net> <20121030132922 DOT GY32696 AT fi DOT muni DOT cz> <201210312340 DOT q9VNe3VW012697 AT envy DOT delorie DOT com> Date: Sun, 4 Nov 2012 09:18:12 -0900 Message-ID: Subject: Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was: Pin hole size) From: Britton Kerin To: geda-user AT delorie DOT com Content-Type: text/plain; charset=ISO-8859-1 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 On Sun, Nov 4, 2012 at 6:55 AM, Kai-Martin Knaak wrote: > Britton Kerin wrote: > >> Its not that the rest is bad information it just lards the docs and >> I doubt its going to give people without any git knowledge enough >> comfort to do anything besides get a copy of the code and maybe mail >> in a patch. >> > Which is already plenty. > I for one, had my first git experience with geda and I appreciated the > scm page in the wiki. I was able to extract the ncessary information > to submit a patch without caring about all the rest of the elephant. I'm confused, are you saying getting clone and how to mail a patch is plenty, and that's what you first did? Because that is the info on that page I would keep. Or are you saying all the rest was useful too (in which case I'm wrong and it should all stay)? I'm sorry I got a bit abrasive with home page criticism etc., its a frustrating situation I feel pretty strongly the people saying the docs have problems are correct, and that creating more documentation is not necessarily the answer but rather consolidating and paring down somewhat, but I guess this is hard to do. Britton