DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=xifsMKzuGB/pl1RV
	1vSEflUx1nQK3jCD57cTn0lXIiG50ZiCbaxcRAnNY2s3GcNHlar5NtopSCpYBLMx
	2KkHa26DrLO23n58XMigyqnGLHGs4JQMbMztJFab2S7fx1E7KVfvkBoQqtyDwaGd
	0kzWulN0YVKc60PJEJ13++L0uHc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <535C0E1C.6050409@cs.umass.edu>
Date: Sat, 26 Apr 2014 15:50:52 -0400
From: Eliot Moss <moss@cs.umass.edu>
Reply-To: moss@cs.umass.edu
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: GIT
References: <0C723FEB5B4E5642B25B451BA57E2730751B9B9A@S1P5DAG3C.EXCHPROD.USA.NET>	<20140425162224.GL5666@calimero.vinschen.de> <87iopxt7tk.fsf@Rainer.invalid>
In-Reply-To: <87iopxt7tk.fsf@Rainer.invalid>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Another suggestion w.r.t. git.  While I realize the
I am perhaps (probably) losing some of the touted
strengths of git, I tend to use it as a front-end
(client side) to subversion repos.  Therefore I
tend to use a simple subversion-like workflow.
It's one way to get started with git.  You could
"branch out" from there (pun intended!).

Best wishes -- Eliot

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple