From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] how to avoid adding labels based on source names
Date: Sun, 3 Jun 2007 14:14:02 -0400 [thread overview]
Message-ID: <20070603181402.GA8650@mona.jeffcovey.net> (raw)
In-Reply-To: <1180325255-sup-6791@south>
on Sun, May 27, 2007 at 09:12:05PM -0700%, William Morgan said:
> > how do i stop sup-sync from adding a label to each message based on the
> > name of its source?
>
> There is currently no way to do this. This is my top priority change at
> the moment.
is there any news on this? there's no rush, but it is the one thing that's
keeping me from trying sup. :)
thanks,
--
jeff covey
http://jeffcovey.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070603/8025892a/attachment.bin
next prev parent reply other threads:[~2007-06-03 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 19:50 jeff covey
2007-05-28 4:12 ` William Morgan
2007-06-03 18:14 ` jeff covey [this message]
2007-06-03 19:20 ` William Morgan
2007-06-04 1:11 ` [sup-talk] gracefully handling missing sources jeff covey
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=20070603181402.GA8650@mona.jeffcovey.net \
--to=jeff.covey@pobox.com \
/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