From 81d55713987dd3b78786132434f0673cfb83ae3e Mon Sep 17 00:00:00 2001 From: Profpatsch Date: Sat, 23 Jan 2021 16:35:54 +0100 Subject: feat(users/Profpatsch/netencode): rename spec -> README Change-Id: I0afda1c3705b8789cf6a0c57f7b74d005deb4ff5 Reviewed-on: https://cl.tvl.fyi/c/depot/+/2433 Reviewed-by: Profpatsch Tested-by: BuildkiteCI --- users/Profpatsch/netstring/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'users/Profpatsch/netstring') diff --git a/users/Profpatsch/netstring/README.md b/users/Profpatsch/netstring/README.md index 4413d88ee430..b8daea11d158 100644 --- a/users/Profpatsch/netstring/README.md +++ b/users/Profpatsch/netstring/README.md @@ -10,7 +10,7 @@ foo! -> 4:foo!, They can be used to encode e.g. lists by simply concatenating and reading them in one-by-one. -If you need a more complex encoding, you could start encoding e.g. tuples as netstrings-in-netstrings, or you could use [`netencode`](../netcencode/spec.md) instead, which is what-if-json-but-netstrings, and takes the idea of netstrings to their logical conclusion. +If you need a more complex encoding, you could start encoding e.g. tuples as netstrings-in-netstrings, or you could use [`netencode`](../netencode/README.md) instead, which is what-if-json-but-netstrings, and takes the idea of netstrings to their logical conclusion. Resources: -- cgit 1.4.1