all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: ofv@wanadoo.es, lekktu@gmail.com, Eli Zaretskii <eliz@gnu.org>,
	jan.h.d@swipnet.se, emacs-devel@gnu.org
Subject: Re: bzr workflow
Date: Wed, 13 Jan 2010 17:48:31 +0900	[thread overview]
Message-ID: <874omq2xwg.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <e01d8a51001122056t6a02eb59le9315c1a307d33b5@mail.gmail.com>

Lennart Borgman writes:

 > >> It would be very good if someone pointed out on the wiki page where
 > >> (and perhaps how) you build Emacs. Do you do that in the trunk
 > >> directory
 > >
 > > Yes.
 > >
 > >> Is there anything special to consider?
 > >
 > > No.  Just do it as usual.
 > 
 > Thanks Eli.
 > 
 > Maybe it should be pointed out somewhere? I am not sure.

I don't think so.  There should not be any problems related to
building, *except* that the workflow common in "small" projects of
using "bzr branch" a lot without a shared repository should be avoided
in Emacs because the overhead of "make bootstrap" is noticable, and
unnecessary with an appropriate workflow.

I think you're the first person I've seen to worry about it, so I
don't think it's a FAQ.  When EmacsForBzrDevs is updated, we can just
add "You can just build and test as usual in the 'trunk' branch if you
use it for quick fixes."





  reply	other threads:[~2010-01-13  8:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 21:10 bzr workflow Sam Steingold
2010-01-11 21:35 ` Andreas Schwab
2010-01-11 21:57   ` Sam Steingold
2010-01-11 23:05     ` Andreas Schwab
2010-01-11 21:37 ` Óscar Fuentes
2010-01-11 22:13   ` Chong Yidong
2010-01-12  7:47   ` Jan Djärv
2010-01-12  8:40     ` Óscar Fuentes
2010-01-12  9:39       ` Jan Djärv
2010-01-12  9:48         ` Óscar Fuentes
2010-01-12 19:41         ` Eli Zaretskii
2010-01-13  7:24           ` Jan D.
2010-01-13  0:01         ` Juanma Barranquero
2010-01-13  2:18           ` Stephen J. Turnbull
2010-01-13  2:16             ` Juanma Barranquero
2010-01-13  3:23               ` Stephen J. Turnbull
2010-01-13  3:29                 ` Lennart Borgman
2010-01-13  4:18                   ` Eli Zaretskii
2010-01-13  4:56                     ` Lennart Borgman
2010-01-13  8:48                       ` Stephen J. Turnbull [this message]
2010-01-13  3:53                 ` Juanma Barranquero
2010-01-13  2:27             ` Karl Fogel
2010-01-13  4:02               ` Stephen J. Turnbull
2010-01-13  4:20                 ` Eli Zaretskii
2010-01-13 16:55                 ` Karl Fogel
2010-01-13  4:17               ` Eli Zaretskii
2010-01-13  8:31               ` Óscar Fuentes
2010-01-12 19:35     ` Eli Zaretskii
2010-01-11 22:08 ` Eli Zaretskii

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=874omq2xwg.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=lekktu@gmail.com \
    --cc=lennart.borgman@gmail.com \
    --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 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.