aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRunxi Yu <me@runxiyu.org>2025-02-14 16:27:36 +0800
committerRunxi Yu <me@runxiyu.org>2025-02-14 16:27:36 +0800
commit81da2c9ca832443f74341de51d5c0ff52b261860 (patch)
tree48d7cbef3e4be602245c0ef20e997bd63eb600ff
parent*_server.go: clog.Info instead of Debug for requests (diff)
downloadforge-81da2c9ca832443f74341de51d5c0ff52b261860.tar.gz
forge-81da2c9ca832443f74341de51d5c0ff52b261860.tar.zst
forge-81da2c9ca832443f74341de51d5c0ff52b261860.zip
README.md: Clarify how MR emails work
-rw-r--r--README.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/README.md b/README.md
index f8ab85d..d29a9ea 100644
--- a/README.md
+++ b/README.md
@@ -71,7 +71,10 @@ the description and manage the MR further via the standard error channel.
MR branches shall be synced to automatically created MR-specific mailing lists.
These mailing lists should have archives accessible via read-only IMAP, JMAP,
-or something else that achieves a similar result.
+or something else that achieves a similar result. Merge requests are presented
+as what would be produced from git-send-email. It should also be possible for
+people to perform code reviews via email by interwoven a quoted patch with
+replies, and all these replies should be synced to the main MR database.
### Ticket tracking