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. 432bc116fb34fd796c70132d184a3e3d1e126b4f
Date: Thu, 23 Apr 2015 23:32:20 +0200	[thread overview]
Message-ID: <20150423213221.1826D21EA6@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1363 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  432bc116fb34fd796c70132d184a3e3d1e126b4f (commit)
      from  991082e93600c3c2ba529ea8bbc0437c5764c964 (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 432bc116fb34fd796c70132d184a3e3d1e126b4f
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Thu Apr 23 23:31:58 2015 +0200

    openssl: fix typo on arm config.

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

Summary of changes:
 lfs/openssl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Difference in files:
diff --git a/lfs/openssl b/lfs/openssl
index 6872f10..699f360 100644
--- a/lfs/openssl
+++ b/lfs/openssl
@@ -66,7 +66,7 @@ endif
 endif
 
 ifeq "$(MACHINE)" "armv5tel"
-	CONFIGURE_OPIONS += linux-generic32
+	CONFIGURE_OPTIONS += linux-generic32
 endif
 
 ###############################################################################


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

                 reply	other threads:[~2015-04-23 21:32 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=20150423213221.1826D21EA6@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