]> git.pond.sub.org Git - empserver/commit
projects / empserver / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d46b168) | patch
Move clear_telegram_is_new() call to beginning of update
authorMarkus Armbruster <armbru@pond.sub.org>
Sun, 20 Nov 2011 17:30:39 +0000 (18:30 +0100)
committerMarkus Armbruster <armbru@pond.sub.org>
Thu, 29 Dec 2011 10:47:06 +0000 (11:47 +0100)
commitac5dac06905e96c8054686af5ac9ecfd31c03e4d
treecdfd7b282a7b66f87636b10140e73ca1c32bfc90tree | snapshot
parentd46b168663f01e572eaafc6cb6d81e98c78a1128commit | diff
Move clear_telegram_is_new() call to beginning of update

The call was added in 4.2.5 "so that the next telegram is flagged as
new and not part of the update".  Since the update sends only
TEL_UPDATE telegrams (the previous commit restored that property), and
nothing else does, the next telegram is flagged as new automatically,
except when it's from the next update.  Document that, and move the
call to a more natural place.
src/lib/update/main.c diff | blob | history
Markus's Wolfpack Empire tree