From: "H.J. Lu" <hjl.tools@gmail.com>
To: Matthias Urlichs <matthias@urlichs.de>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
brobecker@adacore.com, gdb@sourceware.org,
binutils@sources.redhat.com
Subject: Re: time to be serious about dropping CVS
Date: Fri, 01 Jan 2010 17:57:00 -0000 [thread overview]
Message-ID: <6dc9ffc81001010956k63b899a7tf3b7d0c0fe5911bd@mail.gmail.com> (raw)
In-Reply-To: <1262361940.2587.2525.camel@kiste>
On Fri, Jan 1, 2010 at 8:05 AM, Matthias Urlichs <matthias@urlichs.de> wrote:
> SVN is _not_ acceptable for anybody who ever tried to do nontrivial work
> when disconnected, e.g. on an airplane. Among other problems.
>
> Please select a distributed VCS. SVN is not.
>
>
Agreed. I have switched my gcc, binutils, gdb and glibc work to git. It is
so much better than svn. I regularly work on N different patches, each on
a different branch, at the same time. When they are done, I create a new
branch from trunk and do
# git merge
to merge them with minimum editing so that I can test them together.
When something goes wrong, I can fix it on problem branches and
do another merge.
"git revert" was also nice. I have used it more than once when I
checked in something which was totally broken.
BTW, I found this
http://cheat.errtheblog.com/s/git
was helpful to me.
--
H.J.
next prev parent reply other threads:[~2010-01-01 17:57 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
2010-01-01 16:06 ` Matthias Urlichs
2010-01-01 17:57 ` H.J. Lu [this message]
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=6dc9ffc81001010956k63b899a7tf3b7d0c0fe5911bd@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sources.redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=matthias@urlichs.de \
/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