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. 1b169a72daae63d435ee74b7ca9f28f1813fb177
Date: Sat, 12 Dec 2015 18:07:45 +0100	[thread overview]
Message-ID: <20151212170745.DF78821445@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1984 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  1b169a72daae63d435ee74b7ca9f28f1813fb177 (commit)
      from  ca762aaf6e9e0062168b145b935171713c88d2b5 (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 1b169a72daae63d435ee74b7ca9f28f1813fb177
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sat Dec 12 17:06:10 2015 +0000

    Speed up rootfile generation
    
    The old usage of find walked through the entire filesystem tree
    and excluded some paths from being printed. The more efficient
    solution is to skip walking through excluded directories entirely.
    
    This is a slight speedup of the build process by a few minutes.
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

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

Summary of changes:
 lfs/Config | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

Difference in files:
diff --git a/lfs/Config b/lfs/Config
index 415766d..a65b0cf 100644
--- a/lfs/Config
+++ b/lfs/Config
@@ -66,8 +66,9 @@ DIR_TMP     = /tmp
 #
 define FIND_FILES
 	cd $(ROOT)/ && find -mount \
-	-not -path './tools*' -not -path './tmp*' -not -path './usr/src*' -not -path './run/*' \
-	-not -path './dev*' -not -path './proc*' -not -path './install*' | sort
+		\( -path './tools' -or -path './tmp' -or -path './usr/src' \
+		-or -path './run' -or -path './dev' -or -path './proc' \
+		-or -path './install' \) -prune -or -print | sort
 endef
 
 # This is common starting logic for builds.


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

                 reply	other threads:[~2015-12-12 17:07 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=20151212170745.DF78821445@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