This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: GIT
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Fri, 25 Apr 2014 23:31:19 +0200
- Subject: Re: GIT
- Authentication-results: sourceware.org; auth=none
- References: <0C723FEB5B4E5642B25B451BA57E2730751B9B9A at S1P5DAG3C dot EXCHPROD dot USA dot NET> <20140425162224 dot GL5666 at calimero dot vinschen dot de>
Corinna Vinschen writes:
>> > > >Yeah, I'm not exactly looking forward to it since I'm very familiar
>> > > >with CVS or SVN, but have nothing but trouble with git. But since
>> > > >everybody else is so very happy with git, I guess I'll have to adapt.
>> > > >Teeth-gnashingly.
>
> Yeah, I'm trying to get a grip via "the book" http://git-scm.com/book/
My recommendation for newcomers to Git would be to take any
not-too-large Git repository(*) and work out a few dozen ways of
breaking it; then freshly clone it to start over once you've thoroughly
messed it up. Once you've done that a few times and maybe know how to
recover from a few less catastrophic sins (like resetting to where you
didn't want to be and then finding out where the former branch head
was), you should have a good base for deciding what kind of workflow
works for you and Git alike. The thing that Git gets right is that it's
incredibly cheap to make yet another clone or branch for when you want
to try something even remotely risky.
(*) http://repo.or.cz/r/cygwin-setup.git perhaps?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
--
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