sup

commit f9358a0fec7d6afcc6cd3f883e22961a33188c0e
parent 21a81104d0346b931676bddc6b280664f63ab7b1
Author: wmorgan <wmorgan@5c8cc53c-5e98-4d25-b20a-d8db53a31250>
Date:   Mon,  2 Apr 2007 23:07:35 +0000

removed outdated info

git-svn-id: svn://rubyforge.org/var/svn/sup/trunk@372 5c8cc53c-5e98-4d25-b20a-d8db53a31250

Diffstat:

1 file changed, 0 insertions(+), 35 deletions(-)
diff --git a/HACKING b/HACKING
@@ -13,38 +13,3 @@ Coding standards
 - Use as few parentheses as possible.
 - Use {} for one-liner blocks and do/end for multi-line blocks.
 
-How messages are updated in the index
--------------------------------------
-
-Ferret doesn't have any concept of updating; to change message state
-it must be deleted then re-added to the index.
-
-Thus there are a couple situations where we'll have a message to be
-"added", but it already exists in the index, and we need to decide
-which parts of which version to keep:
-
-1. The user has changed the state of the message, e.g. read it or
-   added a user label. In this case we want to use the state of the
-   version in memory, but keep everything else on disk.
-
-   This is the behavior of Index#update_message
-
-2. We've received a new copy of the message. Crucially, this can
-   happen for two different reasons:
-
-   a. The message was sent to a mailing list to which the user is
-      subscribed, and we're now getting that message back, possibly
-      with altered content (subject mangling, signature adding, etc.)
-
-   b. The user has moved the message between sources. E.g. if the
-      primary inbox has a quota, and other sources are on local,
-      quota-less disk, the user may regularly move messages from the
-      inbox to the sources on disk.
-
-   In both of these cases, the solution is to keep the state from the
-   index, but use the new message contents.
-
-   This is the behavior of Index#update_or_add_message, which can be
-   also be called for new message.
-
-