From fb207bb553a9baa183fb6352b55b8fe98af636d3 Mon Sep 17 00:00:00 2001 From: Jordan Bancino Date: Mon, 1 Aug 2022 22:22:43 -0400 Subject: [PATCH] Apply #22 --- site/index.html | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/site/index.html b/site/index.html index bfde38d..954d2c0 100644 --- a/site/index.html +++ b/site/index.html @@ -859,10 +859,11 @@ in the future. If you want to reference a submitted patch in a Matrix message or email, it might be a good idea to link to it in the public patch directory.

-The public patch directory works as follows: as soon as your patch is recieved, -it is downloaded and placed in the ingress/ directory with the -original name it was given. Eventually, it will be assigned an ID and moved -to the p/ directory. There is a permanent link that will +The public patch directory works as follows: when you send your patch to the +Matrix room, it is downloaded by the Telodendria Bot and placed in the +ingress/ directory, named as the message ID. Then, it is +assigned a Telodendria patch ID and copied to the p/ +directory as just ${id}.patch. This is a permanent link that will always reference your patch. Then, your patch is symlinked to the queue/ directory. I have a script that automatically ingresses patches and queues them for me, and I'll use this to review patches. @@ -871,7 +872,8 @@ If your patch is accepted, the queue symlink will be moved to the CVS repository. If you patch is rejected for some reason, its symlink will be moved to the rejected/ directory. Regardless of the state of your patch, it will always remain permalinked in the p/ -directory. +directory, and when it is accepted or rejected, Telodendria Bot will +send a message.

You're always welcome to inquire about rejected patches, and request they be