From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH-insta-save] make the undo hooks also save the threads
Date: Tue, 05 Jan 2010 15:47:08 -0800 [thread overview]
Message-ID: <1262735108-sup-1634@masanjin.net> (raw)
In-Reply-To: <1262731539-29227-1-git-send-email-pi+sup@pihost.us>
Reformatted excerpts from Anthony Martinez's message of 2010-01-05:
> As requested, a patch against insta-save. Hopefully this works out better.
Applied to insta-save and remerged into next. Thanks!
> I generated this by rebasing my local next onto origin/next, then
> checked out a local insta-save and cherry-picked next. There shouldn't
> be any dependences on unpublished commits, though, git says my next is
> only head by this one patch.
Ah, the magic of git!
Thanks for all your recent patches, btw. Top notch stuff.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-01-05 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 6:06 [sup-devel] [PATCH 1/3] punctuate "No new messages." consistently between poll, jump_to_next_new Anthony Martinez
2010-01-04 6:06 ` [sup-devel] [PATCH 2/3] undoing read_and_archive should preserve unread state Anthony Martinez
2010-01-04 6:06 ` [sup-devel] [PATCH 3/3] make the undo hooks also save the threads Anthony Martinez
2010-01-05 21:26 ` William Morgan
2010-01-05 22:45 ` [sup-devel] [PATCH-insta-save] " Anthony Martinez
2010-01-05 22:45 ` [sup-devel] [PATCH] " Anthony Martinez
2010-01-05 23:47 ` William Morgan [this message]
2010-01-05 21:25 ` [sup-devel] [PATCH 2/3] undoing read_and_archive should preserve unread state William Morgan
2010-01-05 21:25 ` [sup-devel] [PATCH 1/3] punctuate "No new messages." consistently between poll, jump_to_next_new 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=1262735108-sup-1634@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