From: Romain Francoise <romain@orebokech.com>
To: emacs-devel@gnu.org
Subject: Re: eshell-defgroup. Do we really need this?
Date: Sun, 03 Aug 2008 21:02:07 +0200 [thread overview]
Message-ID: <87abftq5w0.fsf@elegiac.orebokech.com> (raw)
In-Reply-To: 86iquk1nsk.fsf@lifelogs.com
Ted Zlatanov <tzz@lifelogs.com> writes:
> I can set mine up on Ubuntu 6.x and 7.x and MacOS X. [...] I'll
> do --with-ns, --without-x, and --with-x on MacOS X and just the
> latter two on the Ubuntu systems.
There seems to be some confusion here: are you proposing to set up a
new master instance, or to provide build slaves for my master?
If the former, your buildbot will live at a separate URLs, which may
not be ideal.
If the latter, the commands are defined by the master and you don't
need any config file.
Actually, now that I think about it, we should probably redo the
configuration from scratch and have separate masters for the trunk
and the 22 branch, as Python does...
next prev parent reply other threads:[~2008-08-03 19:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:27 eshell-defgroup. Do we really need this? Alan Mackenzie
2008-07-31 19:17 ` Ted Zlatanov
2008-07-31 19:18 ` Lennart Borgman (gmail)
2008-08-01 15:34 ` Ted Zlatanov
2008-08-01 17:08 ` Romain Francoise
2008-08-01 20:30 ` Ted Zlatanov
2008-08-02 4:18 ` Stephen J. Turnbull
2008-08-04 16:34 ` Ted Zlatanov
2008-08-04 17:49 ` Stephen J. Turnbull
2008-08-04 18:38 ` Ted Zlatanov
2008-08-05 8:20 ` Stephen J. Turnbull
2008-08-05 13:57 ` buildbots (was: eshell-defgroup. Do we really need this?) Ted Zlatanov
2008-08-05 20:25 ` Stephen J. Turnbull
2008-08-08 15:26 ` place to send build failure reports? (was: buildbots) Ted Zlatanov
2008-08-08 15:58 ` place to send build failure reports? Chong Yidong
2008-08-03 19:02 ` Romain Francoise [this message]
2008-08-04 16:31 ` eshell-defgroup. Do we really need this? Ted Zlatanov
2008-08-01 16:10 ` Progress: " Alan Mackenzie
2008-08-07 19:25 ` 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=87abftq5w0.fsf@elegiac.orebokech.com \
--to=romain@orebokech.com \
--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).