From: Sascha Silbe <sascha-ml-reply-to-2010-3@silbe.org>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] my list subscription is broken
Date: Thu, 07 Oct 2010 13:41:44 +0200 [thread overview]
Message-ID: <1286449501-sup-5514@twin.sascha.silbe.org> (raw)
In-Reply-To: <1286421412-sup-6614@zyrg.net>
[-- Attachment #1.1: Type: text/plain, Size: 1044 bytes --]
Excerpts from Rich Lane's message of Thu Oct 07 05:21:15 +0200 2010:
> If there are any bugfixes I haven't responded to please resubmit them.
I have collected all my pending patches (including any discussion) plus
one important fix from Michael Hamann in an mbox [1]. You can add it to
sup using sup-add (giving it a distinctive label), check the discussions
and apply all the patches at once using git am on the mbox.
There are a few other patches in my repository [2], but there's a bug
(progress indicator showing incorrect values on my armel box) I need to
hunt down before posting them.
If you'd prefer some other way to get the patches, please speak up.
Bouncing the patch to the list won't work (mail loop detection),
forwarding most likely messes the patch up (as sup doesn't support
forwarding mails as an attachment) and resending the patch is tedious
and looses previous discussion. So the mbox seemed like the best choice.
Sascha
[1] http://sascha.silbe.org/tmp/sup-pending-patches.mbox
[2] git://git.silbe.org/sup (IPv6 only)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-10-07 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 3:21 Rich Lane
2010-10-07 11:41 ` Sascha Silbe [this message]
2010-10-07 14:45 ` Alvaro Herrera
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=1286449501-sup-5514@twin.sascha.silbe.org \
--to=sascha-ml-reply-to-2010-3@silbe.org \
--cc=rlane@club.cc.cmu.edu \
--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