This is an automated email from the git hooks/post-receive script.

grinorcole-guest pushed a commit to branch master
in repository libthread-tie-perl.

commit dadcd63fa02fbb10b97b56e8bb8aab48f781f01e
Author: Christopher Hoskin <christopher.hos...@gmail.com>
Date:   Sun Mar 1 21:35:47 2015 +0000

    Fix issues with debian/control and POD
---
 .gitignore                  |  1 +
 debian/control              | 35 ++++++++++++++++++-----------------
 debian/patches/fixpod.patch | 25 +++++++++++++++++++++++++
 debian/patches/series       |  1 +
 4 files changed, 45 insertions(+), 17 deletions(-)

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..224e7f0
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+.pc/
diff --git a/debian/control b/debian/control
index 93687eb..eecdcb4 100644
--- a/debian/control
+++ b/debian/control
@@ -29,8 +29,8 @@ Description: alternative separate thread implementation of 
shared variables
  The Thread::Tie module is a proof-of-concept implementation of another 
approach
  to shared variables. Instead of having shared variables exist in all the
  threads from which they are accessible, shared variable exist as "normal",
- unshared variables in a seperate thread. Only a tied object exists in each
- thread from which the shared variable is accesible.
+ unshared variables in a separate thread. Only a tied object exists in each
+ thread from which the shared variable is accessible.
  .
  Through the use of a client-server model, any thread can fetch and/or update
  variables living in that thread. This client-server functionality is hidden
@@ -39,23 +39,24 @@ Description: alternative separate thread implementation of 
shared variables
  .
  The Thread::Tie approach has the following advantages:
  .
- * Memory usage - This implementation circumvents the memory leak that 
currently
-   (threads::shared version 0.90) plagues any shared array or shared hash
-   access.
- * Tieing shared variables - Because the current implementation uses tie-ing,
-   you can not tie a shared variable. The same applies for this implementation
-   you might say. However, it is possible to specify a non-standard tie
-   implementation for use within the thread. So with this implementation you 
can
-   tie() a shared variable. So you could tie a shared hash to a DBM file à la
-   dbmopen() with this module.
+  * Memory usage - This implementation circumvents the memory leak that
+    currently (threads::shared version 0.90) plagues any shared array or shared
+    hash access.
+  * Tieing shared variables - Because the current implementation uses tie-ing,
+    you can not tie a shared variable. The same applies for this implementation
+    you might say. However, it is possible to specify a non-standard tie
+    implementation for use within the thread. So with this implementation you
+    can tie() a shared variable. So you could tie a shared hash to a DBM file à
+    la dbmopen() with this module.
  .
  Of course there are disadvantages to this approach:
  .
- * Pure Perl implementation - This module is currently a pure Perl 
-   implementation. This is ok for a proof of concept, but may need re-
-   implementation in pure XS or in Inline::C for production use.
+  * Pure Perl implementation - This module is currently a pure Perl 
+    implementation. This is ok for a proof of concept, but may need re-
+    implementation in pure XS or in Inline::C for production use.
  .
- * Tradeoff between cpu and memory - This implementation currently uses (much)
-   more cpu than the standard shared variables implementation. Whether this 
-   would still be true when re-implemented in XS or Inline::C, remains to be 
seen.
+  * Tradeoff between cpu and memory - This implementation currently uses (much)
+    more cpu than the standard shared variables implementation. Whether this 
+    would still be true when re-implemented in XS or Inline::C, remains to be
+    seen.
  .
diff --git a/debian/patches/fixpod.patch b/debian/patches/fixpod.patch
new file mode 100644
index 0000000..edfdbcf
--- /dev/null
+++ b/debian/patches/fixpod.patch
@@ -0,0 +1,25 @@
+Description: Add encoding, fix spellings
+Author: Christopher Hoskin <christopher.hos...@gmail.com>
+Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=102433
+Last-Update: 2015-03-01
+--- a/lib/Thread/Tie.pm
++++ b/lib/Thread/Tie.pm
+@@ -275,6 +275,7 @@
+ #---------------------------------------------------------------------------
+ 
+ __END__
++=encoding utf-8
+ 
+ =head1 NAME
+ 
+@@ -348,8 +349,8 @@
+ The Thread::Tie module is a proof-of-concept implementation of another
+ approach to shared variables.  Instead of having shared variables exist
+ in all the threads from which they are accessible, shared variable exist
+-as "normal", unshared variables in a seperate thread.  Only a tied object
+-exists in each thread from which the shared variable is accesible.
++as "normal", unshared variables in a separate thread.  Only a tied object
++exists in each thread from which the shared variable is accessible.
+ 
+ Through the use of a client-server model, any thread can fetch and/or update
+ variables living in that thread.  This client-server functionality is hidden
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 0000000..7a503d4
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+fixpod.patch

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/pkg-perl/packages/libthread-tie-perl.git

_______________________________________________
Pkg-perl-cvs-commits mailing list
Pkg-perl-cvs-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits

Reply via email to