From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, thirteen, updated. ef3bc862489a5dfddd0d242a7eb7a0e545996e04
Date: Wed, 28 Nov 2012 08:49:45 +0100 [thread overview]
Message-ID: <20121128074946.03A3920263@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1383 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, thirteen has been updated
via ef3bc862489a5dfddd0d242a7eb7a0e545996e04 (commit)
from 95c26b24859ac1537c5df79cbfaf3ae732be301d (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 ef3bc862489a5dfddd0d242a7eb7a0e545996e04
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Nov 28 08:49:09 2012 +0100
toolchain: bump version.
-----------------------------------------------------------------------
Summary of changes:
make.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/make.sh b/make.sh
index 7cf5945..94e45ed 100755
--- a/make.sh
+++ b/make.sh
@@ -37,7 +37,7 @@ KVER=`grep --max-count=1 VER lfs/linux | awk '{ print $3 }'`
MACHINE=`uname -m`
GIT_TAG=$(git tag | tail -1) # Git Tag
GIT_LASTCOMMIT=$(git log | head -n1 | cut -d" " -f2 |head -c8) # Last commit
-TOOLCHAINVER=5
+TOOLCHAINVER=6
BUILDMACHINE=$MACHINE
if [ "$MACHINE" = "x86_64" ]; then
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-11-28 7:49 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=20121128074946.03A3920263@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