From: Tero Tilus <tero@tilus.net>
To: Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Label Display; Sorting Alphabetically
Date: Wed, 16 Feb 2011 11:08:04 +0200 [thread overview]
Message-ID: <1297847031-sup-6835@tilus.net> (raw)
In-Reply-To: <1297784079-sup-7440@plc.intranet.plecavalier.com>
Philippe LeCavalier, 2011-02-15 17:37:
> Hi All. Just wondering if there has ever been any consideration to
> sorting labels alphabetically. I'm assuming the way sup displays the
> labels is purely esthetic's?
I assume you are talking about thread index mode. Judging from the
code label order looks purely incidental. And I don't remember there
being any discussion on label sorting. Dump sorts the labels though,
to ease keeping dump in vcs I guess.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-02-16 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 15:37 Philippe LeCavalier
2011-02-16 9:08 ` Tero Tilus [this message]
2011-02-16 13:33 ` Philippe LeCavalier
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=1297847031-sup-6835@tilus.net \
--to=tero@tilus.net \
--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