From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org, binutils@sources.redhat.com
Subject: Re: time to be serious about dropping CVS
Date: Fri, 01 Jan 2010 11:03:00 -0000 [thread overview]
Message-ID: <20100101110227.GL548@adacore.com> (raw)
In-Reply-To: <201001011025.o01APi7b017223@glazunov.sibelius.xs4all.nl>
> I simply cannot wrap my head around git.
I understand how you feel, since I went through the same process,
particularly since I started using it a while ago, when the user
interface was, er, rough. Fortunately, it has come a long way and
is a lot better, now.
I will not deny that learning git takes a bit of effort. But, I truly
wholeheartedly believe that the initial pain is well worth the effort,
because it's going to help save so much time later - everything is easier
and faster with git. There's just this initial hump at the beginning.
There is a great book for learning git relatively quickly, and it is
even available on the web: Pro git. It's one of the rare books that
I read from cover to cover.
http://progit.org/
That being said, we can help you in a way that you will not have to
learn much git. If we ever switch to git, we will provide a detailed
procedure, recipes really, on how to do with git all the usual operations
that most contributors need.
For instance, to put your changes aside, just "git stash". To reapply
them again: "git stash pop". But you'll soon learn that even that is
not easy enough, and before you know it, you'll naturally be using branches.
If you're managing a set of patches (eg for a new port, or a new feature),
you'll love "git rebase".
> If we switch to using git, I'll probably stop contributing to GDB.
We'll have ways to allow you to work comfortably, be it SVN or a git-cvs
server.
--
Joel
next prev parent reply other threads:[~2010-01-01 11:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 8:02 Joel Brobecker
2010-01-01 8:35 ` Eli Zaretskii
2010-01-01 9:00 ` Joel Brobecker
2010-01-01 10:34 ` Eli Zaretskii
2010-01-01 15:39 ` Matthias Urlichs
2010-01-01 15:49 ` Eli Zaretskii
2010-01-01 10:26 ` Mark Kettenis
2010-01-01 10:46 ` Andreas Schwab
2010-01-01 11:03 ` Joel Brobecker [this message]
2010-01-01 16:06 ` Matthias Urlichs
2010-01-01 17:57 ` H.J. Lu
2010-01-01 13:00 ` Joseph S. Myers
2010-01-01 14:18 ` Joel Brobecker
2010-01-02 18:11 ` Christopher Faylor
2010-01-02 19:08 ` Christopher Faylor
2010-01-03 13:52 ` Matthias Urlichs
2010-01-08 12:58 ` Phil Muldoon
2010-01-08 13:08 ` Tristan Gingold
2010-01-08 13:20 ` Joel Brobecker
2010-01-08 13:26 ` Tristan Gingold
2010-01-08 13:13 ` Joel Brobecker
2010-01-08 13:21 ` Jonas Maebe
2010-01-08 13:34 ` Andreas Schwab
2010-01-08 13:14 ` Jonas Maebe
2010-01-08 18:41 ` Michael Snyder
2010-01-08 18:49 ` Paul Koning
2010-12-20 17:35 ` Joseph S. Myers
2010-12-21 3:27 ` Joel Brobecker
2010-12-21 3:46 ` Jim Blandy
2010-12-21 7:16 ` Pascal Obry
2010-12-21 15:14 ` Tom Tromey
2010-12-21 16:15 ` Christopher Faylor
2010-12-21 18:39 ` Joseph S. Myers
2010-12-21 19:26 ` Tom Tromey
2010-12-21 18:42 ` Joseph S. Myers
2010-12-21 19:21 ` DJ Delorie
2010-12-22 15:23 ` Christopher Faylor
2010-12-22 15:29 ` NightStrike
2010-12-22 16:48 ` Joseph S. Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100101110227.GL548@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox