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=simple; d=mail.ud03.udmedia.de; h=
	message-id:date:from:mime-version:to:subject:references
	:in-reply-to:content-type:content-transfer-encoding; s=beta; bh=
	OgfJE51GFqA4AyvGeunE9VBqiXamDD7NdR6RlJ66vIU=; b=dthuoj3F5kcJZ+ae
	7P5fAt/OxnN2F97hlr19c154Mq2hJg4Oq3vaA4o4CIA5+8m3S/pEjjBgMZS6s+mE
	WBWRoa7ZzRWSO0TCX8ROKBc9ionnyZiWyIpdCUp9jWr/GbYj3Em72BjEMKB+dRhh
	N1fjy7YUfYu1dZalB+DZGNyS0S8=
Message-ID: <50978B08.1020301@jump-ing.de>
Date: Mon, 05 Nov 2012 10:46:48 +0100
From: Markus Hitter <mah AT jump-ing DOT de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was:
 Pin hole size)
References: <CANqhZFxYH+Y5U1ai7ey-s+4nz6eYDM2vx3aMDb7WuigNXmi4AQ AT mail DOT gmail DOT com> <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> <CAC4O8c-xvCH8j2h3K3+ymO0Zgbru_JqDavqojY81iT_C=-zPrw AT mail DOT gmail DOT com> <CAGde_xOu96b1jxN1n2km3_OAkX9umshs9FQF+Gdjgsbw_Mt4qQ AT mail DOT gmail DOT com> <CAC4O8c8BiPJSJyvTDs337ix2e==+bLwzz3TgqD8rV+B4TPkSxw AT mail DOT gmail DOT com> <k76358$9fs$1 AT ger DOT gmane DOT org> <CAC4O8c9JM0PsC66_tGAYOGAZx1vUR2ZwJr2dZCKihqt_JdfBWQ AT mail DOT gmail DOT com>
In-Reply-To: <CAC4O8c9JM0PsC66_tGAYOGAZx1vUR2ZwJr2dZCKihqt_JdfBWQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

Am 04.11.2012 19:18, schrieb Britton Kerin:
>
> 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.

I agree with that this is the most important part. Once people have git
and checked out a repo one can easily advise them how to check out a
branch, how to go back a few revisions and similar things. And patches 
made from a local git repo will always nicely fit into the main repo.

This doesn't mean it's forbidden to add a bit more, of course. :-)

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

In my glider club there's a rule: "the person doing a job is also the 
person saying how it is done". Works out pretty well.


Markus

-- 
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. (FH) Markus Hitter
http://www.jump-ing.de/