From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel mailing list <sup-devel@rubyforge.org>
Subject: [sup-devel] topic branch merge report
Date: Thu, 31 Dec 2009 12:31:50 -0800 [thread overview]
Message-ID: <1262291246-sup-2713@masanjin.net> (raw)
Hi all,
I've merged the following branches down to master:
'thread-joining-fix', 'no-mailcap-on-darwin',
'label-list-mode-auto-update', 'interactive-crypto',
'label-list-mode-hooks', 'refine-inbox-mode', 'poll-unusual',
'attach-wildcards', 'order-names-by-date' and 'save-all-attachments'.
Rich, I think I need your help with the two branches 'xapian-bugfix' and
'xapian-message-state', which are generating a conflict for some reason,
and I don't understand the code well enough to resolve. Would you be
able to publish a branch ahead of master that has these two merged?
Thanks!
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2009-12-31 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 20:31 William Morgan [this message]
2009-12-31 21:31 ` Rich Lane
2009-12-31 22:41 ` 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=1262291246-sup-2713@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@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