From: Hamish <dmishd@gmail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [sup-talk] Word wrap for quoted lines
Date: Sun, 29 May 2011 18:32:07 +0100 [thread overview]
Message-ID: <1306690297-sup-4154@whisper> (raw)
In-Reply-To: <1306260795-sup-3474@alvh.no-ip.org>
Excerpts from Alvaro Herrera's message of Tue May 24 19:13:43 +0100 2011:
> Excerpts from Hamish's message of dom may 22 18:47:03 -0400 2011:
> > I've created a wrap_quoted branch and applied this patch to it. If there
> > are no objections I'll merge it into the next branch, probably next
> > weekend.
>
> Tried it from your branch, works great.
OK, this is now merged into the next branch.
Hamish
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2011-05-29 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTimTBRbHOTPDpE=qFZetZyccdCdt6w@mail.gmail.com>
[not found] ` <1305817664-sup-572@localhost>
[not found] ` <1305818177-sup-9473@localhost>
2011-05-22 22:47 ` Hamish
2011-05-24 18:13 ` Alvaro Herrera
2011-05-29 17:32 ` Hamish [this message]
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=1306690297-sup-4154@whisper \
--to=dmishd@gmail.com \
--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