From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. b91c8dd61cda16dba35771a7ccc0673c26a8f83c
Date: Sat, 13 Apr 2013 17:19:34 +0200 [thread overview]
Message-ID: <20130413151934.E2B1C20131@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1895 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 b91c8dd61cda16dba35771a7ccc0673c26a8f83c (commit)
via 4c3b79ae89d460dd9f03663b4e202c574b48ab56 (commit)
from 2a35d6adf9475be6ebdc55230b5bdbc78af14382 (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 b91c8dd61cda16dba35771a7ccc0673c26a8f83c
Merge: 2a35d6a 4c3b79a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Apr 13 17:19:17 2013 +0200
Merge remote-tracking branch 'stevee/bash-completion-update'
commit 4c3b79ae89d460dd9f03663b4e202c574b48ab56
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Sat Apr 13 15:04:51 2013 +0200
bash-completion: Update to 2.1.
This is an update to the latest stable version of bash-completion.
-----------------------------------------------------------------------
Summary of changes:
bash-completion/bash-completion.nm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/bash-completion/bash-completion.nm b/bash-completion/bash-completion.nm
index 2648f96..cf944d3 100644
--- a/bash-completion/bash-completion.nm
+++ b/bash-completion/bash-completion.nm
@@ -4,8 +4,8 @@
###############################################################################
name = bash-completion
-version = 1.99
-release = 2
+version = 2.1
+release = 1
arch = noarch
groups = Development/Languages
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-04-13 15:19 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=20130413151934.E2B1C20131@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