From 87678710135973f72722258e171fc00f85c86ec8 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Fri, 20 Mar 2020 08:18:15 +0000 Subject: rename PublicInbox::SearchMsg => PublicInbox::Smsg Since the introduction of over.sqlite3, SearchMsg is not tied to our search functionality in any way, so stop confusing ourselves and future hackers by just calling it "PublicInbox::Smsg". Add a missing "use" in ExtMsg while we're at it. --- Documentation/technical/data_structures.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Documentation/technical/data_structures.txt') diff --git a/Documentation/technical/data_structures.txt b/Documentation/technical/data_structures.txt index 4de83a77..08dfc7ac 100644 --- a/Documentation/technical/data_structures.txt +++ b/Documentation/technical/data_structures.txt @@ -47,7 +47,7 @@ Per-message classes Our PublicInbox::V2Writable class may have two objects of this type in memory at-a-time for deduplication. -* PublicInbox::SearchMsg - small message skeleton +* PublicInbox::Smsg - small message skeleton Used by: PublicInbox::{NNTP,WWW,SearchIdx} Common abbreviation: $smsg @@ -69,7 +69,7 @@ Per-message classes JWZ's algorithm: . This holds a $smsg and is only used for message threading. This wrapper class may go away in the future and handled - directly by PublicInbox::SearchMsg to save memory. + directly by PublicInbox::Smsg to save memory. As with $smsg objects, there may be hundreds or thousands of these objects in memory at-a-time. -- cgit v1.2.3-24-ge0c7