unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Can NOT bzr the emacs repos (may be bzr has a memory leak)
Date: Tue, 02 Feb 2010 11:53:15 +0100	[thread overview]
Message-ID: <87iqafc3j8.fsf@telefonica.net> (raw)
In-Reply-To: 2e566b9e1002012043m293cd98fg36ebc5d9c4cf5428@mail.gmail.com

"Shaowei Wang (wsw)" <wsw1wsw2@gmail.com> writes:

> I can not use the following command to bzr the emacs repos:
> bzr branch http://bzr.savannah.gnu.org/r/emacs/trunk
>
> The bzr eat up so many memory and take my whole system down.

You forgot one key piece of information: how much memory your system
has?

bzr 2.0.4 will use approx. 1GB of resident memory while branching emacs
with http. Branching from Launchpad with the bzr+ssh protocol requires
about 600MB. For this, you must create an account on Launcpad, import a
public ssh key there and:

bzr lp-login your-launchpad-username
bzr branch lp:emacs

IIRC, bzr 2.1 (which is in RC stage) requires a few hundreds of MB less.

OTOH, some people published tarballs of the emacs `trunk' branch. Links
to them are here on the ml.

> my bzr version is :
> bzr --version
> Bazaar (bzr) 2.0.4
>   Python interpreter: /usr/bin/python 2.6.4
>   Python standard library: /usr/lib/python2.6
>   Platform:
> Linux-2.6.32-ARCH-x86_64-AMD_Athlon-tm-_64_Processor_3200+-with-glibc2.2.5
>   bzrlib: /usr/lib/python2.6/site-packages/bzrlib
>   Bazaar configuration: /home/wsw/.bazaar
>   Bazaar log file: /home/wsw/.bzr.log





  reply	other threads:[~2010-02-02 10:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02  4:43 Can NOT bzr the emacs repos (may be bzr has a memory leak) Shaowei Wang (wsw)
2010-02-02 10:53 ` Óscar Fuentes [this message]
2010-02-03  0:40   ` Shaowei Wang (wsw)
2010-02-03  3:08   ` Giorgos Keramidas
2010-02-02 20:37 ` Glenn Morris
2010-02-03  0:59   ` Shaowei Wang (wsw)

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=87iqafc3j8.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --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 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).