From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: small nnimap doc patch
Date: Mon, 21 Feb 2011 15:14:21 -0800 [thread overview]
Message-ID: <877hctm14i.fsf@gnus.org> (raw)
In-Reply-To: <871v31j8f8.fsf@latte.josefsson.org>
Simon Josefsson <simon@josefsson.org> writes:
> What's the recommended way to send patches now?
Same as before, I guess... Or you could get git commit rights, if you
want. :-) Mail me the output from "htpasswd -n simon", and I'll add
you.
> diff --git a/lisp/nnimap.el b/lisp/nnimap.el
Thanks; applied.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2011-02-21 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 23:04 Simon Josefsson
2011-02-21 23:14 ` Lars Ingebrigtsen [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=877hctm14i.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).