Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: Moving GDB sources to subversion?
Date: Sat, 29 Oct 2005 10:57:00 -0000	[thread overview]
Message-ID: <u4q70si9t.fsf@gnu.org> (raw)
In-Reply-To: <17250.47790.110383.508587@kahikatea.snap.net.nz> (message from Nick Roberts on Sat, 29 Oct 2005 12:56:30 +1300)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sat, 29 Oct 2005 12:56:30 +1300
> Cc: drow@false.org, brobecker@adacore.com, gdb@sources.redhat.com
> 
> We can assume that GCC developers have made a sound technical decision.

Yes, we can assume that.  But no one said that there's only one sound
technical decision.  I'm sure there were downsides to that decision
even in the context of the GCC project (as opposed to a general
decision that _all_ GNU projects should adopt svn).  I'm sure that the
decision they made was influenced, at least to some degree, by the
persons who were involved in making the decision, and by their social
dynamics.

These aspects are different in the GDB case, and, of course, GDB is a
different type of project with different (albeit similar) development
and maintenance patterns and different goals.  It is quite possible
that the same set of considerations as those that were discussed by
the GCC team will, in our case, lead to different conclusions and to
different decisions, that are no less sound and technical.

> We should focus on how GDB development differs from that of GCC and
> whether that difference impacts on the choice of version control
> used.

Yes, 100% agreement here.  But we could also decide not to do this
right now, and instead concentrate on development.  That would be a
sound technical decision as well.

Btw, where's the thread (or threads) in which GCC people discussed
this issue?


  reply	other threads:[~2005-10-29 10:57 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
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     ` Mark Kettenis
2005-10-28 23:56       ` Nick Roberts
2005-10-29 10:57         ` Eli Zaretskii [this message]
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-28 23:25     ` Joel Brobecker
2005-10-28 23:57       ` Christopher Faylor
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=u4q70si9t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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