From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Karl Fogel <karl.fogel@canonical.com>
Cc: Andreas Schwab <schwab@suse.de>,
emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Jason Earl <jearl@notengoamigos.org>
Subject: Re: Bzr switch
Date: Tue, 30 Jun 2009 08:37:53 +0900 [thread overview]
Message-ID: <873a9iy5ke.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87vdmfn1fv.fsf@canonical.com>
Karl Fogel writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > In the Bzr world, there's always something new coming up providing this
> > and that performance improvement. So there's no point waiting for the
> > next one, cause when the time is passed, you'll end up wanting to wait
> > for the next next one, etc... ad nauseam.
>
> I understand what you mean, but This Time Is Different (or so I am told,
> in no uncertain terms, by every Bazaar developer I talk to).
Who are you talking to? The list traffic tells a very different
story. Mark Shuttleworth (Da Beeg Boos) wrote "Thou Shalt Have But
One Bazaar 2 Format", and got *lots* of pushback. AFAIK he gave up;
the Bazaar devs surely act like that pronunciamento is "inoperative".
Robert Collins is *not* on board on "2a", specifically, looms are not
included in 2a, which means at least two variants of 2a will be out
there in the wild for a while. (Silver lining: looms are usable as a
local improvement, you don't actually need them on the server for many
common workflows.) Aaron Bentley is *not* on board on "2a",
specifically nested trees have not landed, but they will. (Emacs
doesn't care, I think, but many projects want nested trees very badly.
It will land, not before 2.0, I suspect, but not too long thereafter.
This will mean a server upgrade, the formats are mutually incompatible
currently AIUI.) Four variants. And counting---don't kid yourself,
there will be more.
IMO (and that of the Python devs, see PEPs 374 and 385), Stefan is
right. You need to settle on a version that's either Available Now or
Coming Soon To A GNU/Linux Distro Near You. People who want to bleed
can always do that (to) themselves. :-)
next prev parent reply other threads:[~2009-06-29 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 13:12 Bzr switch Stefan Monnier
2009-06-28 6:53 ` Karl Fogel
2009-06-28 10:45 ` Daniel Clemente
2009-06-28 10:56 ` Daniel Clemente
2009-06-28 19:55 ` Stefan Monnier
2009-06-28 20:26 ` Karl Fogel
2009-06-28 23:41 ` Stefan Monnier
2009-06-29 3:50 ` Karl Fogel
2009-06-29 23:37 ` Stephen J. Turnbull [this message]
2009-06-29 23:44 ` Miles Bader
2009-06-30 1:14 ` Stephen J. Turnbull
-- strict thread matches above, loose matches on Subject: below --
2009-06-30 2:05 Robert Collins
2009-06-30 10:09 ` Daniel Clemente
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=873a9iy5ke.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=jearl@notengoamigos.org \
--cc=karl.fogel@canonical.com \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@suse.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.