unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: 12302@debbugs.gnu.org
Subject: bug#12302: 24.2.50; Inappropriate warning about site-lisp not existing
Date: Thu, 30 Aug 2012 14:07:42 +0200	[thread overview]
Message-ID: <87a9xcoa5t.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <b6zk5dnr0r.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 29 Aug 2012 20:48:52 -0400")

On Wed, 29 Aug 2012 20:48:52 -0400 Glenn Morris <rgm@gnu.org> wrote:

> Presumably this was an out-of-tree build, 

Indeed it is;

>                                           in which case it is fixed now.

thanks.

Steve Berman





      reply	other threads:[~2012-08-30 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  8:50 bug#12302: 24.2.50; Inappropriate warning about site-lisp not existing Stephen Berman
2012-08-30  0:48 ` Glenn Morris
2012-08-30 12:07   ` Stephen Berman [this message]

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=87a9xcoa5t.fsf@rosalinde.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=12302@debbugs.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).