summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Bremner <david@tethera.net>2019-08-25 08:53:39 -0300
committerDavid Bremner <david@tethera.net>2019-08-25 08:53:39 -0300
commitdf60b61cf0b8bb0f40c0544edb812a1014ed89b8 (patch)
tree26b35a7cc92a4e136e6112bce350e1271cbe0a8a
parentd92184745a7415f6cff411c8fb39019102d6a36a (diff)
Commit Debian 3.0 (quilt) metadata
[dgit (9.7) quilt-fixup]
-rw-r--r--debian/patches/auto-0.1.1-4-d92184745a7415f6cff411c8fb39019102d6a36a-1566734019120
-rw-r--r--debian/patches/series1
2 files changed, 121 insertions, 0 deletions
diff --git a/debian/patches/auto-0.1.1-4-d92184745a7415f6cff411c8fb39019102d6a36a-1566734019 b/debian/patches/auto-0.1.1-4-d92184745a7415f6cff411c8fb39019102d6a36a-1566734019
new file mode 100644
index 0000000..4f0017b
--- /dev/null
+++ b/debian/patches/auto-0.1.1-4-d92184745a7415f6cff411c8fb39019102d6a36a-1566734019
@@ -0,0 +1,120 @@
+From: David Bremner <bremner@debian.org>
+Subject: Automatically generated patch (0.1.1-4)
+
+Last (up to) 3 git changes, FYI:
+
+commit d92184745a7415f6cff411c8fb39019102d6a36a
+Author: David Bremner <david@tethera.net>
+Date: Sun Aug 25 08:53:37 2019 -0300
+
+ changelog for rebuild with current dh-elpa
+
+commit ab2fbc182d7dc5e89a5860f6e5fa2b0aa49d3824
+Author: David Bremner <david@tethera.net>
+Date: Sat Jun 2 20:19:32 2018 -0300
+
+ changelog for byte compilation rebuild
+
+commit 6d8e001cadac18e1e2d7c06400c930991ff55940
+Author: Lev Lamberov <dogsleg@debian.org>
+Date: Sat Apr 7 15:13:53 2018 +0500
+
+ Fix Vcs URLs
+---
+
+--- emacs-epc-0.1.1.orig/readme.md
++++ emacs-epc-0.1.1/readme.md
+@@ -35,12 +35,12 @@ Here is a client code.
+
+ (deferred:$
+ (epc:call-deferred epc 'echo '(10))
+- (deferred:nextc it
++ (deferred:nextc it
+ (lambda (x) (message "Return : %S" x))))
+
+ (deferred:$
+ (epc:call-deferred epc 'add '(10 40))
+- (deferred:nextc it
++ (deferred:nextc it
+ (lambda (x) (message "Return : %S" x))))
+
+ ;; calling synchronously
+@@ -61,12 +61,12 @@ use RPC::EPC::Service;
+
+ sub echo_test {
+ my $methods = {
+-
++
+ 'echo' => [sub {
+ my $args = shift;
+ return $args;
+ },"args","just echo back arguments."],
+-
++
+ 'add' => sub {
+ my $args_ref = shift;
+ my ($a,$b) = @$args_ref;
+@@ -86,7 +86,7 @@ Here is the equivalent server code in em
+ (require 'epcs)
+
+ (let ((connect-function
+- (lambda (mngr)
++ (lambda (mngr)
+ (epc:define-method mngr 'echo (lambda (&rest x) x) "args" "just echo back arguments.")
+ (epc:define-method mngr 'add '+ "args" "add argument numbers.")
+ )) server-process)
+@@ -133,11 +133,11 @@ Let we define the words *server* and *cl
+
+ This diagram shows the API usage and the relation of processes.
+
+-![API Overview](/usr/share/doc/elpa-epc/Overview.png)
++![API Overview](img/Overview.png)
+
+ ### Object Serialization
+
+-All values which are transferred as arguments and return values between processes, are encoded into the S-expression text format.
++All values which are transferred as arguments and return values between processes, are encoded into the S-expression text format.
+
+ Simple list structure and some primitive types can be transferred. Complicated objects, such as buffer objects, can not be serialized. The EPC stack doesn't provide transparent remote object service, that is ORB.
+
+@@ -279,7 +279,7 @@ Here is a sample code for the EPC server
+ (require 'epcs)
+
+ (let ((connect-function
+- (lambda (mngr)
++ (lambda (mngr)
+ (epc:define-method mngr 'echo (lambda (x) x) "args" "just echo back arguments.")
+ (epc:define-method mngr 'add '+ "args" "add argument numbers.")
+ )) server-process)
+@@ -317,7 +317,7 @@ The EPC has a management interface for t
+
+ Executing `M-x epc:controller`, one can display the list of current established connections.
+
+-![Current Connections](/usr/share/doc/elpa-epc/mm-conns.png)
++![Current Connections](img/mm-conns.png)
+
+ This table shows following information:
+
+@@ -346,7 +346,7 @@ One can use following key-bind:
+
+ Displaying a method list, one can inspect the methods which are defined by the remote process.
+
+-![Remote Method List](/usr/share/doc/elpa-epc/mm-methods.png)
++![Remote Method List](img/mm-methods.png)
+
+ This table shows following information:
+
+@@ -433,11 +433,11 @@ The EPC is developed on `deferred.el` an
+
+ The EPC user should learn asynchronous programing on `deferred.el`. The components of `concurrent.el` are just internally used at `epc.el`.
+
+-![EPC Stack](/usr/share/doc/elpa-epc/epc-stack.png)
++![EPC Stack](img/epc-stack.png)
+
+ Here is a diagram for the `epc.el` architecture, which diagram may be helpful for code reading of `epc.el`.
+
+-![Internal Architecture](/usr/share/doc/elpa-epc/epc-internal.png)
++![Internal Architecture](img/epc-internal.png)
+
+ ## Other Stacks
+
diff --git a/debian/patches/series b/debian/patches/series
index e266796..478593f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
fix-documentation.diff
+auto-0.1.1-4-d92184745a7415f6cff411c8fb39019102d6a36a-1566734019