From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Official Git mirror?
Date: Wed, 23 Feb 2011 07:32:51 -0500 [thread overview]
Message-ID: <E1PsDtj-0002FN-Sg@fencepost.gnu.org> (raw)
In-Reply-To: <xeia62sb157p.fsf@kobe.laptop> (message from Giorgos Keramidas on Wed, 23 Feb 2011 10:16:10 +0100)
> From: Giorgos Keramidas <keramida@ceid.upatras.gr>
> Newsgroups: gnu.emacs.help
> Date: Wed, 23 Feb 2011 10:16:10 +0100
>
> I started a new 'bzr branch' this morning, when I got to the office,
> using the nosmart option. It's been running for more than an hour now,
> it has transferred 500 MB of data, and all this on a laptop running
> Ubuntu 10.10 LTS with ample free disk space and connected to the very
> fast internal network of Google.
Like I said, the nosmart operation moves about 780MB of data on the
initial "bzr branch" command. The resulting branch directory is
around 690MB. With git, I get 632MB and 780MB respectively (but that
includes all the branches, so it should be larger).
> This is a *lot* of data for something that is supposed to fetch only the
> trunk of Emacs.
The trunk (or, actually, the first branch you download into a shared
repository) brings in the bulk of the revision history. Additional
branches are mush smaller and their checkouts are much faster, because
they share a lot of revisions with the trunk, and "bzr branch" then
brings only the revisions that are not on the trunk. Try another
branch command for emacs-23, for example.
> It took 3989.501 real / 581.270 user / 15.990 sys
> seconds to fetch everything and the resulting .bzr/ directory contains
> 233 MB of data:
>
> gkeramidas@gkeramidas-glaptop:~/bzr/trunk$ du -sh .bzr/
> 233M .bzr/
About an hour is what we can get now, yes (I got as little as 16 min,
but that was on a system sitting on the same LAN as
bzr.savannah.gnu.org; otherwise, I get between 0:45 and 1:10).
> This is not very fast, but I'll keep using the bzr branch to see how
> future updates go.
Please don't forget NOT to use nosmart+ after the initial branch
command.
next prev parent reply other threads:[~2011-02-23 12:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 21:11 Official Git mirror? Oleksandr Gavenko (aka gavenkoa)
2011-02-20 21:35 ` Eli Zaretskii
2011-02-20 21:59 ` Oleksandr Gavenko (aka gavenkoa)
2011-02-21 6:58 ` Eli Zaretskii
2011-02-21 23:29 ` Oleksandr Gavenko
2011-02-22 10:54 ` Eli Zaretskii
[not found] ` <mailman.8.1298372068.26362.help-gnu-emacs@gnu.org>
2011-02-24 19:31 ` Vagn Johansen
2011-02-24 19:55 ` Eli Zaretskii
2011-02-21 5:36 ` Óscar Fuentes
2011-02-21 6:58 ` Leo
2011-02-21 7:58 ` Eli Zaretskii
2011-02-21 16:09 ` Óscar Fuentes
2011-02-21 18:56 ` Eli Zaretskii
2011-02-21 20:08 ` Óscar Fuentes
[not found] ` <mailman.11.1298266625.16274.help-gnu-emacs@gnu.org>
2011-02-21 8:52 ` Tim X
2011-02-21 14:31 ` Official Git mirror? -- Request Perry Smith
2011-02-21 14:57 ` andrea crotti
2011-02-21 18:17 ` Official Git mirror? Óscar Fuentes
2011-02-21 19:02 ` Eli Zaretskii
2011-02-21 19:40 ` Óscar Fuentes
2011-02-21 20:33 ` Eli Zaretskii
2011-02-21 20:57 ` Óscar Fuentes
2011-02-21 21:15 ` Eli Zaretskii
[not found] ` <mailman.11.1298320422.21303.help-gnu-emacs@gnu.org>
2011-02-23 9:16 ` Giorgos Keramidas
2011-02-23 12:32 ` Eli Zaretskii [this message]
2011-02-23 19:38 ` jun yu
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=E1PsDtj-0002FN-Sg@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).