From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] new in next: faster saving and bigger indexes
Date: Thu, 28 Feb 2008 16:28:22 -0800 [thread overview]
Message-ID: <1204244881-sup-2122@south> (raw)
In-Reply-To: <1204239818-sup-9440@tomsk>
Reformatted excerpts from Marcus Williams's message of 2008-02-28:
> I just did an update but didnt get anything new other than the pgp
> stuff. You sure its in next? :)
Should be: commit 28f7a766f32040f993af88dae9fe2d994a80f16c.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-02-29 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 17:15 William Morgan
2008-02-27 15:19 ` Marcus Williams
2008-02-27 17:16 ` William Morgan
2008-02-28 18:25 ` William Morgan
2008-02-28 23:05 ` Marcus Williams
2008-02-29 0:28 ` William Morgan [this message]
2008-02-29 1:27 ` William Morgan
2008-02-27 18:55 ` Christopher Warrington
2008-02-28 17:23 ` William Morgan
2008-03-03 7:42 ` Christopher Warrington
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=1204244881-sup-2122@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