all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: improve vc-bzr-print-log
Date: Mon, 27 Jul 2009 10:54:47 +0900	[thread overview]
Message-ID: <877hxu6gbc.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <200907262155.n6QLtQk4013442@godzilla.ics.uci.edu>

Dan Nicolaescu writes:

 > The thing is that bzr users have all the reasons to use very up to date
 > versions, the performance and disk usage is dramatically better.

All true, but the bzr developers themselves worry about this,
especially because even Ubuntu releases lag bzr releases by many
months, and other distros are even more conservative.

bzr is also not yet out of the woods with respect to "format churn"
(in terms of released versions); there's another big one on the way in
the next month (that is, the recently released as "optional" in 1.17
"--2a" format will become "default" in 2.0, unless of course they have
to retrench on 2.0 and it becomes 1.18 instead, in which case who
knows what will happen to the status of "--2a" format or when it will
become default and eventually propagate into the distros).

I realize that "Emacs developers" won't have a problem with adopting a
bzr recent enough for Emacs developer problems (many are already
following bzr.dev, I suspect), but it's definitely a barrier to entry
for new contributors (something that comes up frequently on the bazaar
list).




  reply	other threads:[~2009-07-27  1:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26 17:28 improve vc-bzr-print-log Dan Nicolaescu
2009-07-26 19:37 ` Chong Yidong
2009-07-26 21:55   ` Dan Nicolaescu
2009-07-27  1:54     ` Stephen J. Turnbull [this message]
2009-08-13 17:28     ` Chong Yidong
2009-08-13 17:40       ` Dan Nicolaescu
2009-07-27  2:50 ` Stefan Monnier

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=877hxu6gbc.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=cyd@stupidchicken.com \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@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 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.