public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, master, updated. a41302651055f03f27c8132526a3bd5520875555
Date: Tue, 03 Jan 2012 21:22:59 +0100	[thread overview]
Message-ID: <20120103202259.E3C61200D6@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1385 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, master has been updated
       via  a41302651055f03f27c8132526a3bd5520875555 (commit)
      from  0d738d2385f637d6ca94c655aa61042e85a5f750 (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 a41302651055f03f27c8132526a3bd5520875555
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Tue Jan 3 21:21:26 2012 +0100

    make.sh: fix wrong md5sum messages at wrong arch packages.

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

Summary of changes:
 make.sh |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

Difference in files:
diff --git a/make.sh b/make.sh
index 1edcf15..ccdb4c6 100755
--- a/make.sh
+++ b/make.sh
@@ -1002,6 +1002,7 @@ downloadsrc)
 	ERROR=0
 	for i in *; do
 		if [ -f "$i" -a "$i" != "Config" ]; then
+			lfsmakecommoncheck ${i} > /dev/null || continue
 			make -s -f $i LFS_BASEDIR=$BASEDIR MACHINE=$MACHINE \
 				MESSAGE="$i\t " md5 >> $LOGFILE 2>&1
 			if [ $? -ne 0 ]; then


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

                 reply	other threads:[~2012-01-03 20:22 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=20120103202259.E3C61200D6@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