From: itaylor@uark.edu (Ian Taylor)
Subject: [sup-talk] new messages don't seem to have NEW status
Date: Fri, 21 Sep 2007 13:14:25 -0400 [thread overview]
Message-ID: <1190394617-sup-276@zap> (raw)
I'm not sure when this started happening (maybe under a week), but any
new message I receive isn't being marked as unread or new.
I disabled all my hooks to ensure that this wasn't the problem, but no
luck.
Is this the case for anyone else? I'm using latest from svn.
--
Ian Taylor, Technical Assistant
Computer Science Computer Engineering
http://www.csce.uark.edu itaylor at uark.edu
University of Arkansas
next reply other threads:[~2007-09-21 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 17:14 Ian Taylor [this message]
2007-09-21 18:52 ` William Morgan
2007-09-22 7:02 ` Ian Taylor
2007-09-24 2:16 ` William Morgan
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=1190394617-sup-276@zap \
--to=itaylor@uark.edu \
/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