unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail]
Date: Wed, 04 Dec 2013 09:50:44 +0100	[thread overview]
Message-ID: <87a9ghngnv.fsf@zigzag.favinet> (raw)
In-Reply-To: <87eh5uqka9.fsf@zigzag.favinet> (Thien-Thi Nguyen's message of "Tue, 03 Dec 2013 11:51:58 +0100")

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

() Thien-Thi Nguyen <ttn@gnu.org>
() Tue, 03 Dec 2013 11:51:58 +0100

   Now i see e/.git/bzr/.bzr/repository/upload/ w/ a slowly-growing
   .pack file (294MB at the moment).  I suppose this is a temporary work
   area for git-remote-bzr and the working tree e/ will be populated
   once download is complete.

   So far, so good.  (Now watch the gods strike me and my old computer
   down -- Murphy's Law...)

Ah yes, Mr. Murphy.  After four hours, the hard disk filled up (5.8 G is
apparently not enough) and the process exited failurefully.  The good
(?) news is that the death was clean, and apart from a huge increase in
entropy, there remains no sign of activity whatsoever.  I and my old
computer thank you for dropping by.  :-/

I'm curious: What is the maximum transient disk footprint people see for
"git clone bzr::..." and for a "pure bzr" (no git-bzr) checkout?  Is
there a huge difference?  How about footprint after successful checkout?

[If anyone wants to donate me a new(er) computer for Emacs (and other
 Free Software) hacking, please contact me off-list.]

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2013-12-04  8:50 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 17:32 Latest changes with lisp/uni-*.el and leim/quail Eli Zaretskii
2013-11-28 20:36 ` Glenn Morris
2013-11-29  8:42   ` Eli Zaretskii
2013-11-29 13:46     ` Stefan Monnier
2013-11-29 14:25       ` Eli Zaretskii
2013-11-29 16:43         ` Stefan Monnier
2013-11-29  7:46 ` Dani Moncayo
2013-11-29  8:38   ` Eli Zaretskii
2013-11-29  9:03     ` Dani Moncayo
2013-11-29 20:10       ` Glenn Morris
2013-11-29 21:40         ` Dani Moncayo
2013-11-30  0:37           ` participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail] Drew Adams
2013-11-30  4:47             ` Jambunathan K
2013-11-30  8:36               ` Eli Zaretskii
2013-11-30  8:43                 ` Dani Moncayo
2013-11-30 11:04                   ` Eli Zaretskii
2013-11-30 11:11                   ` Jarek Czekalski
2013-11-30 23:05                     ` Drew Adams
2013-12-01  7:26                       ` Thien-Thi Nguyen
2013-12-01  7:27                         ` Jambunathan K
2013-12-02 13:29                         ` Rüdiger Sonderfeld
2013-12-02 13:37                           ` Jarek Czekalski
2013-12-03 10:51                           ` Thien-Thi Nguyen
2013-12-03 20:03                             ` Wolfgang Jenkner
2013-12-03 20:33                               ` Andreas Schwab
2013-12-03 20:55                                 ` Wolfgang Jenkner
2013-12-03 21:18                                   ` Andreas Schwab
2013-12-04  8:50                             ` Thien-Thi Nguyen [this message]
2013-12-04 10:05                               ` Andreas Schwab
2013-12-04 13:52                                 ` Stefan Monnier
2013-12-04 13:57                                   ` Andreas Schwab
2013-12-08 11:01                                 ` adventures w/ git-bzr Thien-Thi Nguyen
2013-12-01  7:50                       ` participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail] Thien-Thi Nguyen
2013-12-01  8:09                         ` Jambunathan K
2013-11-30  8:47                 ` Jambunathan K
2013-11-30 13:50                 ` Stefan Monnier
     [not found] <<83txew8m9v.fsf@gnu.org>
     [not found] ` <<CAH8Pv0hxmFCoEgd6Wag93LAuNy0JPPJ6UNjt3xcWjNdKAB=K5A@mail.gmail.com>
     [not found]   ` <<837gbr8uxa.fsf@gnu.org>
     [not found]     ` <<CAH8Pv0g0P7x=_KOmV2737AJpHgDEJu6_ecdmBseU6rVDuTzKQw@mail.gmail.com>
     [not found]       ` <<lubo13dl4n.fsf@fencepost.gnu.org>
     [not found]         ` <<CAH8Pv0h-7J-N-Drhc4vNw=26LtK4YShep0cuDXQeoPjLgqfvoQ@mail.gmail.com>
     [not found]           ` <<f527b11d-f842-4426-8e41-4991f9abe40c@default>
     [not found]             ` <<87wqjqts1b.fsf@gmail.com>
     [not found]               ` <<83zjom5ls5.fsf@gnu.org>
2013-11-30 18:41                 ` Drew Adams
2013-12-01  0:05                   ` Karl Fogel
2013-12-01 17:39                     ` Stephen J. Turnbull
2013-12-01 18:33                       ` Karl Fogel
2013-12-01 19:03                       ` Stefan Monnier

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=87a9ghngnv.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --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).