From: B Smith-Mannschott <bsmith.occs@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: bzr branch makes bogus "No space left on device" claim and dies
Date: Fri, 8 Jan 2010 19:36:30 +0100 [thread overview]
Message-ID: <28c656e21001081036y3bce45fen3f8245168dc145d5@mail.gmail.com> (raw)
In-Reply-To: <87iqbfnc7p.fsf@red-bean.com>
Thanks to all who helped me out. I've now got a working repository of
emacs with a branch of savannah's emacs trunk and lauchpad's emacs
trunk. I've been pulling my updates through the launchpad branch for
the most part. Performance is acceptable for my purposes.
When building from source on my netbook, I've discovered that I can do
a bzr checkout --lightweight to a ramdisk.The resulting working copy
can then be used to build emacs and thrown away when I'm done. Nice.
And I've already learned the difference between branch and checkout as
well as playing with --lightweight. I can see where the bzr can claim
workflow flexibility. It's just a pity that some combinations of http,
sftp, branch, checkout, leightweight, init, init-repo, etc can produce
performance surprises for the uninitiated.
// Ben
next prev parent reply other threads:[~2010-01-08 18:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 15:11 bzr branch makes bogus "No space left on device" claim and dies B Smith-Mannschott
2010-01-05 20:50 ` Bojan Nikolic
2010-01-06 10:17 ` B Smith-Mannschott
2010-01-06 13:12 ` Eli Zaretskii
2010-01-06 14:09 ` B Smith-Mannschott
2010-01-07 9:32 ` B Smith-Mannschott
2010-01-07 14:48 ` Stefan Monnier
2010-01-08 21:03 ` B Smith-Mannschott
2010-01-06 3:28 ` Karl Fogel
2010-01-06 10:26 ` B Smith-Mannschott
2010-01-07 14:10 ` B Smith-Mannschott
2010-01-07 15:14 ` Karl Fogel
2010-01-07 15:21 ` B Smith-Mannschott
2010-01-07 17:44 ` Stephen J. Turnbull
2010-01-07 19:45 ` Stefan Monnier
2010-01-07 19:58 ` B Smith-Mannschott
2010-01-08 18:36 ` B Smith-Mannschott [this message]
2010-01-07 11:40 ` Sascha Wilde
2010-01-07 11:45 ` B Smith-Mannschott
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=28c656e21001081036y3bce45fen3f8245168dc145d5@mail.gmail.com \
--to=bsmith.occs@gmail.com \
--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.