unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: William Xu <william.xwl@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: Re: mac emacs port busted.
Date: Thu, 01 Nov 2007 22:38:18 +0900	[thread overview]
Message-ID: <m27il25bn9.fsf@gmail.com> (raw)
In-Reply-To: 1193520711.965845.120540@22g2000hsm.googlegroups.com

Daniel Engeler <engeler@gmail.com> writes:

> Is there no automatic build on all platforms after each check-in?

Maybe never... Emacs supports so many platforms..

-- 
William





  reply	other threads:[~2007-11-01 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2215.1192653101.18990.bug-gnu-emacs@gnu.org>
2007-10-27 21:31 ` mac emacs port busted Daniel Engeler
2007-11-01 13:38   ` William Xu [this message]
2007-10-17 20:31 Doug Turner

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=m27il25bn9.fsf@gmail.com \
    --to=william.xwl@gmail.com \
    --cc=bug-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.
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).