all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Earl <jearl@xmission.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: dhruva <dhruva@ymail.com>, Emacs Development <emacs-devel@gnu.org>
Subject: Re: Requesting bzr repository of emacs on savannah
Date: Fri, 05 Sep 2008 12:38:19 -0600	[thread overview]
Message-ID: <874p4u8mlg.fsf@xmission.com> (raw)
In-Reply-To: <jwvod32tybp.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 05 Sep 2008 11:27:16 -0400")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>>  I have been using the bzr repository of emacs from:
>>  http://bzr.notengoamigos.org/emacs/trunk/.  I am using the development
>>  version of bzr and things have improved in terms of
>>  performance.  I have also been lurking on the #bzr IRC channel and see
>>  a lot of positive vibes and focus on improving performance.
>
>>  At this juncture, I request (once again) to the emacs maintainers to
>>  request savannah hackers to setup a read only bzr repository for
>>  emacs.  I did chat on the #savannah on IRC and was told that the
>>  project maintainers need to make a request and they can easily do it.
>
>>  The main reason I am making this request is that connectivity to
>>  "bzr.notengoamigos.org" is slow and affects the perception of bzr
>>  user.  From 2 days, my connection is breaking mid way and prevents me
>>  from pulling changes.  I am looking for something more reliable.
>
> I've been using a bzr branch for my own local branch and basically use
> bzr for everything except "commit to trunk", ever since the
> bzr.notengoamigos.org mirror was setup.  Performance of bzr seems OK
> for my use nowadays.  I.e. we could switch to bzr "any time".  The
> main hurdle for now is that the bzr.notengoamigos.org itself is not
> quite good enough and lacks all the merge info from Miles's Arch
> mirror (it also lacks the file-move info).

I'm really sorry that I haven't made any more progress on this front.  I
just graduated, and that took up a much larger amount of time than I
would have guessed (which is probably why I hadn't graduated earlier :).

I have been experimenting with several ways of getting a better bzr
repository for Emacs, but I just haven't had time to track down the bugs
in the import process that I have run into.

Of course, if anyone else is interested in taking a crack that this
problem I would certainly appreciate the help :).

> So a new conversion of the CVS repository to bzr is needed that will
> fix those problem.  We could switch to bzr as soon as this is done.
> 
> As for the speed of bzr.notengoamigos.org, I haven't noticed it being
> slow (but then again I update every day or so, and usually at times
> when I do other things anyway).  But there's a copy of that branch up on
> http://arch.savannah.gnu.org/archives/emacs/bzr/trunk, which any member
> of the "emacs" group can update via sftp.

bzr.notengoamigos.org is pretty well hosted.  If anyone has problems
updating their branches form there I would be interested in hearing
about it.  That's especially true if you start from one of the pre-made
bzr repositories that I have at the site.

I have seen problems with updates if the branch the person is updating
from gets changed, but that shouldn't be a problem if you aren't pulling
down all 100,000 changesets.




      parent reply	other threads:[~2008-09-05 18:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20  3:34 Requesting bzr repository of emacs on savannah dhruva
2008-09-05 15:27 ` Stefan Monnier
2008-09-05 16:09   ` René Kyllingstad
2008-09-05 16:57     ` Phil Hagelberg
2008-09-05 17:55       ` Miles Bader
2008-09-06  7:44       ` Teemu Likonen
2008-09-06 12:31         ` Lennart Borgman (gmail)
2008-09-06 13:00           ` Teemu Likonen
2008-09-05 18:19     ` joakim
2008-09-06  7:12     ` Richard M. Stallman
2008-09-05 18:38   ` Jason Earl [this message]

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=874p4u8mlg.fsf@xmission.com \
    --to=jearl@xmission.com \
    --cc=dhruva@ymail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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.