all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Kevin Ryde <user42@zip.com.au>
Cc: 6596@debbugs.gnu.org
Subject: bug#6596: 23.2; cl.texi docs loop destructuring for alist
Date: Thu, 22 Jul 2010 20:47:56 -0700 (PDT)	[thread overview]
Message-ID: <201007230347.o6N3lu7E017639@godzilla.ics.uci.edu> (raw)
In-Reply-To: <877hknvx47.fsf@blah.blah> (Kevin Ryde's message of "Fri, 23 Jul 2010 10:51:36 +1000")

Kevin Ryde <user42@zip.com.au> writes:

  > Glenn Morris <rgm@gnu.org> writes:
  > >
  > > The entire repo is 339MB.
  > 
  > Yes, I thought so, that's too much really, especially if the updates are
  > as bad as rumour has it.
  > 
  > > I don't think that is massively bigger than a CVS checkout used to be.
  > 
  > If the size on disk is a good guide it was between 30 and 50 mb
  > compressed, and of course you could get just the part you wanted to work
  > on, or a few files at a time.  :-(
  > 
  > > I hope you can make it work somehow, since committers are in short
  > > supply.
  > 
  > Alas, doomed for the time being I think.  I've removed my savannah
  > member thing for now to avoid confusion.

You could get an account on the GCC farm:

http://gcc.gnu.org/wiki/CompileFarm#How_to_Get_Involved.3F

quite a few machines are provided, with decent disk space and
connectivity...





  reply	other threads:[~2010-07-23  3:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 23:44 bug#6596: 23.2; cl.texi docs loop destructuring for alist Kevin Ryde
2010-07-11  2:13 ` Glenn Morris
2010-07-13  1:50   ` Kevin Ryde
2010-07-13 15:49     ` Glenn Morris
2010-07-16  1:19       ` Kevin Ryde
2010-07-16 16:12         ` Glenn Morris
2010-07-21 15:21           ` Stefan Monnier
2010-07-23  0:51           ` Kevin Ryde
2010-07-23  3:47             ` Dan Nicolaescu [this message]
2011-07-14  0:15 ` Lars Magne Ingebrigtsen

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=201007230347.o6N3lu7E017639@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=6596@debbugs.gnu.org \
    --cc=user42@zip.com.au \
    /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.