gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-marketing] branch master updated: minor comment change


From: gnunet
Subject: [taler-marketing] branch master updated: minor comment change
Date: Fri, 25 Sep 2020 11:30:42 +0200

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

dold pushed a commit to branch master
in repository marketing.

The following commit(s) were added to refs/heads/master by this push:
     new c3f6543  minor comment change
c3f6543 is described below

commit c3f654303ac73300ef521f27c2ede85c1921f3bd
Author: Florian Dold <florian.dold@gmail.com>
AuthorDate: Fri Sep 25 15:00:25 2020 +0530

    minor comment change
---
 standards/rfc8905-in-prep.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/standards/rfc8905-in-prep.xml b/standards/rfc8905-in-prep.xml
index 7aea5e9..a71fa1a 100644
--- a/standards/rfc8905-in-prep.xml
+++ b/standards/rfc8905-in-prep.xml
@@ -518,7 +518,7 @@ Template on https://www.iana.org/assignments/uri-schemes/:
 
    References: See References section of RFC-dold-payto-14.
 
-Reply-CG:
+Answer-CG:
    I don't see a reason to duplicate it here.
 -->
 
@@ -851,7 +851,7 @@ Original:
    [GANA]     GNUnet e.V., "GNUnet Assigned Numbers Authority (GANA)",
               April 2020, <https://gana.gnunet.org/>.
 
-Reply-CG:
+Answer-CG:
   The "git.gnunet.org" URL is only going to work as long as GANA uses the
   GNUnet Git repository. Using the top-level alias is likely a more stable
   URL. Finding the payto registry within GANA should be reasonably simple.
@@ -863,7 +863,7 @@ use.
 "Payment Target Types" sub-registry
 "payto-payment-target-typesā€¯ registry
 
-Reply-CG:
+Answer-CG:
   I have changed the text to always use "Payto Payment Target Types" registry
   when referencing the registry at GANA.
 
@@ -889,7 +889,7 @@ objections.
 
 payto vs. 'payto'
 
-Reply:
+Answer-CG:
   This is fine.
 -->
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]