From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] PATCH: make each thread's snippet come from the latest reply, not the earliest
Date: Sat, 27 Oct 2007 15:24:08 -0700 [thread overview]
Message-ID: <1193523470-sup-442@south> (raw)
In-Reply-To: <6ab4c98f0710231455w68f89232r527b8d4b43e9e16f@mail.gmail.com>
Excerpts from Phil Snowberger's message of Tue Oct 23 14:55:58 -0700 2007:
> Attached is a patch (against the SVN trunk) that makes each thread's
> snippet come from the latest reply instead of the earliest.
Applied, in modified form, even though I'm really supposed to be
focusing on bug fixes right now.
> p.s. Thanks for sup, William! It's just what I wanted, but I hadn't
> realized what I wanted until I saw it :)
Thanks! Added to the Wall of Praise.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-10-27 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 21:55 Phil Snowberger
2007-10-27 22:24 ` William Morgan [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=1193523470-sup-442@south \
--to=wmorgan-sup@masanjin.net \
/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