public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9e8a51306a41bac6d71b853c92893fa6a500ba3b
Date: Sun, 15 Feb 2015 19:56:30 +0100	[thread overview]
Message-ID: <20150215185630.AC44E21A83@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  9e8a51306a41bac6d71b853c92893fa6a500ba3b (commit)
      from  00548de4ad0a02524e8fa88e6c4605e65e151f6a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 9e8a51306a41bac6d71b853c92893fa6a500ba3b
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sun Feb 15 19:55:56 2015 +0100

    dnsmasq: Disable using inotify
    
    The ISC reader code won't work without inotify

-----------------------------------------------------------------------

Summary of changes:
 lfs/dnsmasq | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Difference in files:
diff --git a/lfs/dnsmasq b/lfs/dnsmasq
index 244077c..d4eb9d4 100644
--- a/lfs/dnsmasq
+++ b/lfs/dnsmasq
@@ -32,7 +32,8 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 
-COPTS      = -DHAVE_ISC_READER
+# We cannot use INOTIFY because our ISC reader code does not support that
+COPTS      = -DHAVE_ISC_READER -DNO_INOTIFY
 
 ###############################################################################
 # Top-level Rules


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2015-02-15 18:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150215185630.AC44E21A83@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox