unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: Angelo Graziosi <angelo.graziosi@alice.it>, emacs-devel@gnu.org
Subject: Re: BZR and the bootstrap
Date: Mon, 09 Aug 2010 20:53:37 +0900	[thread overview]
Message-ID: <87sk2oxari.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87wrs02gro.fsf@telefonica.net>

Óscar Fuentes writes:
 > Angelo Graziosi <angelo.graziosi@alice.it> writes:
 > 
 > [snip]
 > 
 > > So, which is the best tree for bootstrap?
 > >
 > > BTW, 'emacs-trunk' has a '.bzr' file of 226 M!

That's not bad, considering you can produce nearly 100,000 different
versions of Emacs from that with "bzr revert -r NNN" for NNN a
positive integer.  (It's a little more complicated than that, actually
but not much.)

 > Can you afford those 226 MB? If yes, go with the normal checkout.

+1.

You really do not want to do rsync against an active tree; there are
no consistency guarantees with rsync.  (Rsync will deliver files
correctly, I believe, but there's no guarantee that will correspond to
a version of Emacs that ever existed in any developer's workspace.)

The normal checkout is, indeed, overkill if you only ever intend to
update to latest.  However, you will often see posts saying that the
bootstrap is broken since revno 89444 or something like that, and you
can get back to something sane, *without* needing to talk to Savannah
or Launchpad, with a simple "bzr revert -r 89443".  Also, if you ever
feel the need to make a change (and I hope you will!), it's much
easier to manage those changes if you have a full local branch.




  reply	other threads:[~2010-08-09 11:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07 16:49 BZR and the bootstrap Angelo Graziosi
2010-08-09  2:55 ` Eli Zaretskii
2010-08-09  3:37   ` Óscar Fuentes
2010-08-09  6:57     ` Stephen J. Turnbull
2010-08-09  8:57       ` Angelo Graziosi
2010-08-09  9:52         ` Angelo Graziosi
2010-08-09 10:59           ` Óscar Fuentes
2010-08-09 11:53             ` Stephen J. Turnbull [this message]
2010-08-09 10:57       ` Óscar Fuentes
2010-08-09 11:57         ` Stephen J. Turnbull
2010-08-09 17:12           ` Eli Zaretskii
2010-08-09 17:11       ` Eli Zaretskii
2010-08-09 21:47         ` Angelo Graziosi
2010-08-09 21:59           ` Óscar Fuentes
2010-08-09 19:42   ` Johan Bockgård
2010-08-10  6:19     ` Eli Zaretskii
2010-08-10  7:32       ` Kenichi Handa
2010-08-10  9:20         ` Stefan Monnier
2010-08-10 17:26           ` Eli Zaretskii
2010-08-10  7:27     ` 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=87sk2oxari.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=angelo.graziosi@alice.it \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /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).