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=
	ers2xtd9w328RBYyergsewqld+my6R/NM4F82WRL+JM=; b=B8363Nl33Wc8jkay
	vUZEWRq+n2za7I7LjtpdW/4GptOjCqlEibPYjPD9acf/4BEJfEZvgJxH+6r8Cd/D
	kdKXu4R02n8oM7wNpCjo/GY0IW6h5QFsxrDgDP+8ZXw1e85t5vLxKonSLLig/pgH
	GkM79RSfz33tb/QoevB64lPN434=
Message-ID: <50964B74.9040205@jump-ing.de>
Date: Sun, 04 Nov 2012 12:03:16 +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>
In-Reply-To: <CAC4O8c8BiPJSJyvTDs337ix2e==+bLwzz3TgqD8rV+B4TPkSxw@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 03.11.2012 23:10, schrieb Britton Kerin:
> I think this page replaces most of it:
>
>    http://www.kernel.org/pub/software/scm/git/docs/everyday.html

I had more success with Wine's Git descriptions:

http://wiki.winehq.org/GitWine#head-20352a9b6bbab91763387de5b12a36a9fecc87b0

Also, I think this "sending patches" mechanism they ask for would be a 
nice fit for the casual gEDA developer. Doing so is straightforward:

1 - Commit the change(s) in as many commits you see fit in your local 
repo. In doubt, more commits with smaller changes in each are better.

2 - Do a    git format-patch --keep-subject origin/master

3 - You'll get numbered file(s), starting with 0001-... Send them to 
this list as-is or - even better - open a bug on Launchpad and attach 
them there. They'll be easy to apply.


- - -

Also, gitk is IMHO worth a few words of mentioning. Simple to install 
and use and helps greatly keeping the overview over what happens in the 
repo. Just do a menu -> file -> reload before and after every action.


my $0.02
Markus

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