Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: col@baibell.org (Colin Bell)
Subject: [sup-talk] [PATCH] Show unread message count in thread index
Date: Mon, 05 Nov 2007 21:01:31 +1100	[thread overview]
Message-ID: <1194256715-sup-4315@lankhmar> (raw)

Hi,

This patch shows the unread message count in the thread index as well
as the total number of messages in the thread.

E.G:


2:17pm Marcus,Grant,William (1/ 3)  [sup-talk] [PATCH] Check IMAP
2:15pm Marcus,William       (0/ 2)  [sup-talk] [PATCH] More IMAP/

--
Col

-------------- next part --------------
A non-text attachment was scrubbed...
Name: unread.diff
Type: application/octet-stream
Size: 1745 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071105/167121b3/attachment.obj 


             reply	other threads:[~2007-11-05 10:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 10:01 Colin Bell [this message]
2007-11-07  2:09 ` William Morgan
2007-11-07  3:55   ` Colin Bell
2007-11-07 10:29   ` Colin Bell
2007-11-07 20:08     ` William Morgan
2007-11-07 21:09       ` Marcus Williams
2007-11-07 23:12         ` William Morgan
2007-11-08  8:31           ` Marcus Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1194256715-sup-4315@lankhmar \
    --to=col@baibell.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox