all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Karl Fogel <karl.fogel@canonical.com>
Cc: Andreas Schwab <schwab@suse.de>,
	Jason Earl <jearl@notengoamigos.org>,
	emacs-devel@gnu.org
Subject: Re: Bzr switch
Date: Mon, 29 Jun 2009 01:41:43 +0200	[thread overview]
Message-ID: <jwvr5x4ue23.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ws6wnlza.fsf@canonical.com> (Karl Fogel's message of "Sun, 28 Jun 2009 16:26:33 -0400")

>> Actually, I don't have a preference for that format.  If I had
>> a preference it'd be for the 1.9 format.
> I strongly recommend the new format.  It is faster and smaller, in ways
> that will make a difference for a large, deep-history project like Emacs.
> In particular, 'log -v' times are faster, though I wish they were faster
> still.

I don't care much about such incremental improvements.  Factors of 2 are
nice but don't change my point of view: having to manually install Bzr
just to access Emacs's repository is a bad idea.
Especially given that the format can be changed in the future, so
there's no reason to hurry up adoption of the new format.

> Yes.  Again, I'd like to just give Bazaar 1.16.1 a couple of weeks more
> testing -- I don't want to ask the Savannah admins to upgrade only to
> have to ask them to do it again shortly afterwards.  I'm keeping an eye

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.

> No objection to starting testing earlier, of course!  Just in terms of
> my own schedule, and a desire to avoid doing work twice, I'm planning to
> wait a couple of weeks before making any noises at Savannah.  If anyone
> wants to take this and run with it sooner, though, I'm all in favor.

I'd much rather work on getting the 1.9 format working on Savannah right
now, so we can switch to Bzr ASAP.
Of course, Jason tells me that the conversion is currently broken for
non-bleeding-edge formats, so maybe the 1.9 format is not really an
option.


        Stefan




  reply	other threads:[~2009-06-28 23:41 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 [this message]
2009-06-29  3:50         ` Karl Fogel
2009-06-29 23:37           ` Stephen J. Turnbull
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=jwvr5x4ue23.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jearl@notengoamigos.org \
    --cc=karl.fogel@canonical.com \
    --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.