all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: BZR and the bootstrap
Date: Mon, 09 Aug 2010 10:57:41 +0200	[thread overview]
Message-ID: <4C5FC305.30102@alice.it> (raw)
In-Reply-To: <874of4l1cp.fsf@uwakimon.sk.tsukuba.ac.jp>

Il 09/08/2010 8.57, Stephen J. Turnbull ha scritto:
> Óscar Fuentes writes:
>
>   >  >  Nothing bad should happen, because if I'm right, Emacs invokes
>   >  >  "bzr status" which is done entirely locally.
>
>   >  He says that the modem lights blink, indicating network
>   >  activity.

Right!

>   >  So it seems that the OP is using a lightweight
>   >  checkout.

Wow! Oscar, you have a crystal ball!! Really I did

$ bzr checkout --lightweight http://bzr.savannah.gnu.org/r/emacs/trunk 
emacs-trunk

the first time I used BZR!

>   >  If that is true, I wonder what info bzr needs from
>   >  upstream.

Indeed...

>
> Everything.  From the help message:
>
> Usage:   bzr checkout [BRANCH_LOCATION] [TO_LOCATION]
>
> Options:
>    --lightweight         Perform a lightweight checkout.  Lightweight checkouts
>                          depend on access to the branch for every operation.
>
> It's penny-wise and pound-foolish for anybody who is unfamiliar with
> Bazaar to use lightweight checkouts.  Occasional contributors and beta
> testers should invest in a full branch, bound or not depending on
> their use cases.

So, what is it the best way to create the development source tree of Emacs?

Is, perhaps, the following?

$ bzr checkout http://bzr.savannah.gnu.org/r/emacs/trunk emacs-trunk

I wonder if there is a way that uses 'rsync', instead, like TeXLive[*]...

Ciao,
Angelo.

---
[*] http://www.tug.org/texlive/svn :

"You can retrieve the entire development source tree via rsync:
rsync -a --delete --exclude=.svn tug.org::tldevsrc ."



  reply	other threads:[~2010-08-09  8:57 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 [this message]
2010-08-09  9:52         ` Angelo Graziosi
2010-08-09 10:59           ` Óscar Fuentes
2010-08-09 11:53             ` Stephen J. Turnbull
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C5FC305.30102@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    --cc=stephen@xemacs.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.