From: Simon Richter <Simon.Richter@hogyros.de>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com
Subject: Re: Moving GDB sources to subversion?
Date: Fri, 28 Oct 2005 22:53:00 -0000 [thread overview]
Message-ID: <4362ABD1.8040508@hogyros.de> (raw)
In-Reply-To: <20051028222253.GX1155@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Hi,
Joel Brobecker schrieb:
> I think GCC is getting ready to move to subversion as the revision
> control system. Is there any similar plan for GDB?
At present, there appears to be a SCM war going on, with everyone trying
to pull as many projects towards their side as possible. As a cogito
fan, I'm no exception to that :-). I personally don't like svn for the
simple reason that it provides no substantial improvement over CVS. It
is still centrally organized and works best if only a core group who
knows the system by heart commits patches, in case they need to be
merged; at the same time, it has a very informal notion of branches and
tags, which is a great disadvantage in my opinion.
I've learned to live with CVS by using a cronjob that incrementally
imports new commits into my working tree, which happens to be git-based;
a similar thing could be done to create a SVN repository that tracked
CVS and allowed people to use svn if happens to be their preferred tool.
Using svn for the master tree would make this difficult because of the
aforementioned informality on branches and tags; an import script would
be forced to use heuristics to properly determine them.
Simon
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 374 bytes --]
next prev parent reply other threads:[~2005-10-28 22:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 22:23 Joel Brobecker
2005-10-28 22:53 ` Simon Richter [this message]
2005-10-28 22:56 ` Mark Kettenis
2005-10-28 23:02 ` Joel Brobecker
2005-10-28 23:04 ` Andreas Tobler
2005-10-28 23:08 ` Ian Lance Taylor
2005-10-29 0:15 ` H. J. Lu
2005-10-28 23:14 ` Daniel Jacobowitz
2005-10-28 23:25 ` Joel Brobecker
2005-10-28 23:57 ` Christopher Faylor
2005-10-28 23:25 ` Mark Kettenis
2005-10-28 23:56 ` Nick Roberts
2005-10-29 10:57 ` Eli Zaretskii
2005-10-30 0:11 ` Ian Lance Taylor
2005-10-30 4:27 ` Eli Zaretskii
2005-10-30 2:47 ` Bob Rossi
2005-10-30 4:38 ` Ian Lance Taylor
2005-10-30 4:56 ` Daniel Jacobowitz
2005-11-07 0:27 ` Daniel Jacobowitz
2005-10-29 2:49 ` Stan Shebs
2005-11-02 22:56 ` Jim Blandy
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=4362ABD1.8040508@hogyros.de \
--to=simon.richter@hogyros.de \
--cc=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
/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