aboutsummaryrefslogtreecommitdiff
path: root/open_issues/anatomy_of_a_hurd_system.mdwn
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2024-04-07 17:18:07 +0200
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2024-04-07 17:18:07 +0200
commit0db356ea482b3045f4d49b5c7953791bf18573a3 (patch)
treed083419e0fb7f974b4111a5fcd44174d1d221556 /open_issues/anatomy_of_a_hurd_system.mdwn
parent9553439d7562aad9c3b58a83fc7c0059fc29422a (diff)
downloadweb-0db356ea482b3045f4d49b5c7953791bf18573a3.tar.gz
web-0db356ea482b3045f4d49b5c7953791bf18573a3.tar.bz2
web-0db356ea482b3045f4d49b5c7953791bf18573a3.zip
Fix git.savannah.gnu.org urls into https
Diffstat (limited to 'open_issues/anatomy_of_a_hurd_system.mdwn')
-rw-r--r--open_issues/anatomy_of_a_hurd_system.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/open_issues/anatomy_of_a_hurd_system.mdwn b/open_issues/anatomy_of_a_hurd_system.mdwn
index 82f2333c..9232186f 100644
--- a/open_issues/anatomy_of_a_hurd_system.mdwn
+++ b/open_issues/anatomy_of_a_hurd_system.mdwn
@@ -1050,12 +1050,12 @@ Actually, the Hurd has never used an M:N model. Both libthreads (cthreads) and l
<teythoon> as I said, the wire format is specified, the semantics only in
written form in the source
<teythoon> this is an example of the ipc specification for the proc server
- http://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/hurd/process.defs
+ https://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/hurd/process.defs
<crocket> teythoon, how file server interacts with file clients should be
defined as a formal protocol, too.
<teythoon> do you consider the ipc description a kind of formal protocol ?
<crocket>
- http://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/hurd/process.defs can
+ https://git.savannah.gnu.org/cgit/hurd/hurd.git/tree/hurd/process.defs can
be considered as a formal protocol.
<crocket> However, the file server protocol should be defined on top of IPC
protocol.