From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 414ca3fe85d1fbaed8e775926166f19c158ea836
Date: Wed, 10 Apr 2019 22:00:49 +0100 [thread overview]
Message-ID: <20190410210050.167F984FDAF@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1488 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 3.x development tree".
The branch, master has been updated
via 414ca3fe85d1fbaed8e775926166f19c158ea836 (commit)
from f48d90546c8840e021ae45532378b97b55fd27a8 (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 414ca3fe85d1fbaed8e775926166f19c158ea836
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Apr 9 20:59:21 2019 +0100
binutils: Update to 2.32
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
binutils/binutils.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/binutils/binutils.nm b/binutils/binutils.nm
index 81e7884a2..b971bb375 100644
--- a/binutils/binutils.nm
+++ b/binutils/binutils.nm
@@ -4,7 +4,7 @@
###############################################################################
name = binutils
-version = 2.30
+version = 2.32
release = 1
maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2019-04-10 21:00 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=20190410210050.167F984FDAF@people01.i.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