From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] merge activity report
Date: Thu, 28 May 2009 08:13:56 -0700 [thread overview]
Message-ID: <1243523591-sup-5117@entry> (raw)
In-Reply-To: <1242667096-sup-7844@ntdws12.chass.utoronto.ca>
Reformatted excerpts from Ben Walton's message of 2009-05-18:
> Let me know when you'd like the flexible sent stuff rebased and
> against which branch. I'm ready with that any time.
Sorry for the delay on this. I've merged down everything related so a
rebase against master should be pretty easy for you. Once that's done
I will merge it into next.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-05-28 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 15:11 William Morgan
2009-05-18 17:19 ` Ben Walton
2009-05-18 18:24 ` William Morgan
2009-05-28 15:13 ` William Morgan [this message]
2009-05-28 15:31 ` Ben Walton
2009-05-28 16:37 ` William Morgan
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=1243523591-sup-5117@entry \
--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