Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] can't remove draft label
Date: Wed, 30 Jan 2008 23:08:09 -0700	[thread overview]
Message-ID: <1201759596-sup-4274@tangerine.lanl.gov> (raw)
In-Reply-To: <1201754138-sup-7276@chris-tablet>

Excerpts from Christopher Warrington's message of Wed Jan 30 21:36:09 -0700 2008:
> Excerpts from John Bent's message of Wed Jan 30 12:05:20 -0600 2008:
> > I had two messages that weren't drafts that kept showing up with
> > draft labels on them.  I removed everything from the .sup/drafts
> > folder - no change.  I did 'sup-tweak-labels --remove draft' on my
> > mbox, it said:
> > 
> > Scanned 13 / 13 messages and changed 13.
> > 
> > At which point, I restarted sup and found that one of the two falsely
> > labeled drafts was removed.  But there's still one.  I retried the
> > sup-tweak-labels but to no avail.  draft is not a user supplied label
> > so just editing the message labels doesn't work.  The thread that is
> > marked as a draft does not have a draft anywhere in it (i.e. I skip to
> > each message and hit 'e' but it always says, "this isn't a draft").
> > 
> > Any ideas?  Thanks!
> 
> Try
> 
> sup-sync --changed sup://drafts
> 
Thanks so much for the suggestion.  :)
I thought it worked because I saw this message:

Deleting missing messages from the index...
Deleted 1 / 1 messages

But that was just the message I'd previously deleted from the drafts dir.
The false draft is still there... 


  reply	other threads:[~2008-01-31  6:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 18:05 John Bent
2008-01-31  4:36 ` Christopher Warrington
2008-01-31  6:08   ` John Bent [this message]
2008-02-03  4:44     ` William Morgan
2008-03-20 22:37       ` John Bent

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=1201759596-sup-4274@tangerine.lanl.gov \
    --to=johnbent@lanl.gov \
    /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