unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Alan Mackenzie <acm@muc.de>, Chad Brown <yandros@mit.edu>,
	emacs-devel@gnu.org
Subject: Re: What have the Romans done for us? (Bazaar)
Date: Mon, 5 Apr 2010 16:06:57 -0700	[thread overview]
Message-ID: <m2h97cbfe491004051606jee82372ewb8621f9f4947f688@mail.gmail.com> (raw)
In-Reply-To: <jwvaath3cdy.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]

On Mon, Apr 5, 2010 at 12:56 PM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:

> > While I'm no real fan of bazaar, wait until we want to merge the
> > gtk-tabs branch, or the bidi branch, or the lexbind branch, or (even
> > better) more than one of those into the mainline, and I think you'll
> > see a a big difference versus cvs.
>
> No, *he* (like most people) won't.  And it's not going to be
> significantly easier than when we did it in the (near) past, because we
> already used to do it in a DVCS (namely Arch) thanks to Miles's mirror.
>
> But yes, for the person handling the merge (and even more so for the
> person who maintains the branch until it gets merged), it helps a lot.


I take your point, but my thought (perhaps not well-enough explained) was
that he (and we) would feel the benefits of it even if it was only
vicariously avoiding pain.

Let me put this another way:  If multi-tty was any indication, the sorts of
efforts represented by bidi, gtk-tabs, concurrent, and guile would be
suppressed/discouraged/obscured by a non-distributed system like cvs
compared to the ``here's my live repo'' state we have now, and we have been
very conservative in our adoption of dvcs system benefits (as evidenced by
the periodic ``why are we still doing this crud if we're using a dvcs?''
threads).

In the meantime, I'm now using bzr, because of emacs -- which I believe was
the (regardless of technical merit) reason that we adopted the system.
 Probably at least several others here are as well, so there's hope for it
to improve, as long as the growing pains aren't too onerous.

Thanks for your time.

[-- Attachment #2: Type: text/html, Size: 2071 bytes --]

  reply	other threads:[~2010-04-05 23:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 14:56 What have the Romans done for us? (Bazaar) Alan Mackenzie
2010-04-05 15:32 ` Karl Fogel
2010-04-05 16:08   ` Andreas Schwab
2010-04-05 20:54     ` Karl Fogel
2010-04-05 21:11       ` Andreas Schwab
2010-04-05 21:19         ` Andreas Schwab
2010-04-05 16:40   ` Eli Zaretskii
2010-04-05 19:44     ` Stefan Monnier
2010-04-05 22:01       ` Eli Zaretskii
2010-04-05 20:56     ` Karl Fogel
2010-04-05 19:39   ` Óscar Fuentes
2010-04-06 14:31   ` Alan Mackenzie
2010-04-06 15:24     ` Andreas Schwab
2010-04-06 17:02     ` Chad Brown
2010-04-06 19:50       ` Juri Linkov
2010-04-07  6:33     ` Eli Zaretskii
2010-04-07 18:47     ` Stephen J. Turnbull
2010-04-05 15:34 ` Eli Zaretskii
2010-04-05 15:43   ` Andreas Schwab
2010-04-05 16:42     ` Eli Zaretskii
2010-04-05 19:52     ` Stefan Monnier
2010-04-06 10:43     ` Richard Stallman
2010-04-07 18:11       ` Stephen J. Turnbull
2010-04-05 16:01 ` Chad Brown
2010-04-05 19:56   ` Stefan Monnier
2010-04-05 23:06     ` chad [this message]
2010-04-06  7:14       ` Stephen J. Turnbull
2010-04-05 16:12 ` Chong Yidong
2010-04-06 10:43 ` Richard Stallman
2010-04-06 13:25   ` Alan Mackenzie
2010-04-12  5:04     ` Martin Pool
2010-04-06 14:35 ` Jason Rumney
2010-04-06 16:20   ` Alan Mackenzie
2010-04-07 18:21     ` Stephen J. Turnbull
2010-04-07 20:38 ` Óscar Fuentes

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=m2h97cbfe491004051606jee82372ewb8621f9f4947f688@mail.gmail.com \
    --to=yandros@gmail.com \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yandros@mit.edu \
    /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).