From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] [PATCH] Allow thread index view to sort oldest first
Date: Thu, 01 Oct 2009 10:43:25 -0700 [thread overview]
Message-ID: <1254418822-sup-7654@yoom.home.cworth.org> (raw)
In-Reply-To: <1254416597-sup-8156@masanjin.net>
Excerpts from William Morgan's message of Thu Oct 01 10:04:52 -0700 2009:
> I am interested in trying these changes but I think these patches were
> generated against a custom version of master (e.g. I see the inbox
> refine-search command in the context, which hasn't been published yet).
Guilty as charged.
> Can you rebase them onto a recent non-modified master so that I can
> apply? Thanks!
See the attached patches.
And as before, the behavior is split into two commits so that you can
decide whether to change the default or not.
And there's still the one minor bug that the oldest-first mode doesn't
actually guarantee that the oldest message is displayed first when
newer messages arrive for an old thread.
-Carl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Allow-thread-index-view-to-sort-oldest-first.patch
Type: application/octet-stream
Size: 7502 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20091001/ec87d014/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Change-the-default-sort-for-inbox-mode-to-be-oldest-.patch
Type: application/octet-stream
Size: 777 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20091001/ec87d014/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20091001/ec87d014/attachment.bin>
next prev parent reply other threads:[~2009-10-01 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 21:08 Carl Worth
2009-10-01 17:04 ` William Morgan
2009-10-01 17:43 ` Carl Worth [this message]
2009-10-12 12:48 ` William Morgan
2009-10-12 23:02 ` Carl Worth
2009-10-13 20:51 ` Olly Betts
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=1254418822-sup-7654@yoom.home.cworth.org \
--to=cworth@cworth.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