From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 7f88a71f90f733c2004bcaeeb9633fc51d2b049a
Date: Thu, 21 Mar 2013 12:28:22 +0100 [thread overview]
Message-ID: <20130321112822.E3EF72047D@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1446 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 7f88a71f90f733c2004bcaeeb9633fc51d2b049a (commit)
from 431c0e69bcfc86bec5892c44a1ffc7dfc712fa37 (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 7f88a71f90f733c2004bcaeeb9633fc51d2b049a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Mar 21 12:28:08 2013 +0100
vlan: Cannot be built in parallel.
-----------------------------------------------------------------------
Summary of changes:
lfs/vlan | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/vlan b/lfs/vlan
index 9d07c28..6e862b9 100644
--- a/lfs/vlan
+++ b/lfs/vlan
@@ -70,7 +70,7 @@ $(subst %,%_MD5,$(objects)) :
$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
- cd $(DIR_APP) && make $(MAKETUNING) purge vconfig
+ cd $(DIR_APP) && make purge vconfig
cd $(DIR_APP) && install -c -p -m 0755 vconfig /sbin
@rm -rf $(DIR_APP)
@$(POSTBUILD)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-03-21 11:28 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=20130321112822.E3EF72047D@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