From: Philippe LeCavalier <support@plecavalier.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] stripping label from msgs
Date: Tue, 01 Feb 2011 12:43:59 -0500 [thread overview]
Message-ID: <1296582225-sup-7780@plc.intranet.plecavalier.com> (raw)
In-Reply-To: <1296581380-sup-1179@tilus.net>
Excerpts from Tero Tilus's message of Tue Feb 01 12:31:59 -0500 2011:
> Philippe LeCavalier, 2011-02-01 18:29:
> > I've only recently began using sup. As such, I've changed my mind on
> > my labeling structure.
>
> You probably want to make friends with sup-tweak-labels. And thats
> _after_ you have backed up label state dump. ;)
>
> sup-tweak-labels --help
>
Perfect!
--
Thanks,
Phil
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-02-01 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 16:29 Philippe LeCavalier
2011-02-01 17:26 ` Michael Stapelberg
2011-02-01 19:58 ` Philippe LeCavalier
2011-02-01 20:18 ` sup-talk-bounces
2011-02-01 17:31 ` Tero Tilus
2011-02-01 17:43 ` Philippe LeCavalier [this message]
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=1296582225-sup-7780@plc.intranet.plecavalier.com \
--to=support@plecavalier.com \
--cc=sup-talk@rubyforge.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