From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 6ba1bd0031fe2b77a69e441d5da0bb3dfdd07ed6
Date: Sat, 12 Jan 2013 20:56:23 +0100 [thread overview]
Message-ID: <20130112195624.76BB8200D4@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1535 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 6ba1bd0031fe2b77a69e441d5da0bb3dfdd07ed6 (commit)
from 3994dee19059cb0c20cd666b3c2ccb633e504f88 (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 6ba1bd0031fe2b77a69e441d5da0bb3dfdd07ed6
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Sat Jan 12 18:35:54 2013 +0100
git: Fix packaging of SVN.pm.
The SVN.pm was packaged wrong. Moved it to the correct package (git-Perl-SVN).
-----------------------------------------------------------------------
Summary of changes:
git/git.nm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/git/git.nm b/git/git.nm
index 29bf935..cae8af2 100644
--- a/git/git.nm
+++ b/git/git.nm
@@ -5,7 +5,7 @@
name = git
version = 1.8.1
-release = 2
+release = 3
groups = Development/Tools
url = http://git-scm.com/
@@ -232,6 +232,7 @@ packages
files
%{mandir}/man3/Git::SVN*
+ %{perl_vendorlib}/Git/SVN*.pm
%{perl_vendorlib}/Git/SVN/
end
end
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2013-01-12 19:56 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=20130112195624.76BB8200D4@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