unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Yavor Doganov <yavor@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: dVCS vs. CVS
Date: Tue, 08 Jan 2008 21:59:56 +0900	[thread overview]
Message-ID: <87lk70mq0j.fsf@catnip.gol.com> (raw)
In-Reply-To: <87myrg7jki.GNU's_Not_Unix!%yavor@gnu.org> (Yavor Doganov's message of "Tue, 08 Jan 2008 11:28:13 +0200")

Yavor Doganov <yavor@gnu.org> writes:
> I'm not defending CVS and do not dispute the many advantages of dVCS.
> I am just disappointed that nearly all projects ignore the drawbacks
> they bring in to non-technical people.

Your description below makes it sounds like the (presumed) disadvantage
is not from dCVS per-se, but rather simply from _any_ change in tools.

It's true that a project probably shouldn't be changing the tools it
uses too often (that just confuses everybody), but I think change is
inevitable in the long run, and in the long run I'm not sure it makes
much difference whether it happens tuesday or thursday...

-Miles

-- 
"Suppose we've chosen the wrong god. Every time we go to church we're
just making him madder and madder." -- Homer Simpson

  reply	other threads:[~2008-01-08 12:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06 14:01 dVCS vs. CVS Bastien
2008-01-07 15:23 ` Yavor Doganov
2008-01-07 16:03   ` Tassilo Horn
2008-01-07 21:00     ` Alan Mackenzie
2008-01-07 22:45       ` Tassilo Horn
2008-01-08  2:46         ` Michael Olson
2008-01-08  9:28     ` Yavor Doganov
2008-01-08 12:59       ` Miles Bader [this message]
2008-01-07 16:05   ` David Kastrup
2008-01-07 21:52     ` Bastien
2008-01-07 21:59     ` Stephen J. Turnbull
2008-01-07 22:19       ` David Kastrup
2008-01-08  8:57         ` Stephen J. Turnbull
2008-01-09 11:37           ` Richard Stallman
2008-01-07 22:33       ` Bastien

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lk70mq0j.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=yavor@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).