From: Phil Hagelberg <phil@hagelb.org>
To: 5521@debbugs.gnu.org
Subject: bug#5521: Works for me
Date: Sun, 7 Feb 2010 09:41:31 -0800 [thread overview]
Message-ID: <31edf1081002070941xed3b410rf6619baef8f7f2e@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1002040254510.27997@octopus.pepperfish.net>
I've tested this patch, and it works great for me. Thanks to Vivek for
submitting it!
-Phil
next prev parent reply other threads:[~2010-02-07 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 2:58 bug#5521: 23.1; erc - allow autojoin to be delayed till after services ident Vivek Dasmohapatra
2010-02-07 17:41 ` Phil Hagelberg [this message]
2010-06-27 12:36 ` bug#5521: Deniz Dogan
2010-07-16 16:24 ` bug#5521: Seems to work Criveti Mihai
2010-07-17 23:37 ` bug#5521: 23.1; erc - allow autojoin to be delayed till after services ident Chong Yidong
2010-07-18 4:21 ` Michael Olson
[not found] ` <AANLkTimNL_9MS9bAQcp6Bc3d_n6A9JyUBA1lY3TSjjX7@mail.gmail.com>
2010-08-14 22:58 ` Chong Yidong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31edf1081002070941xed3b410rf6619baef8f7f2e@mail.gmail.com \
--to=phil@hagelb.org \
--cc=5521@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).