From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Phil Hudson <phil.hudson@iname.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Patches sent
Date: Mon, 09 May 2016 12:11:53 +0200 [thread overview]
Message-ID: <87r3dbzgk6.fsf@saiph.selenimh> (raw)
In-Reply-To: <877ff3inhl.fsf@quiz.hudson-it.ddns.net> (Phil Hudson's message of "Mon, 09 May 2016 10:34:14 +0100")
Hello,
Phil Hudson <phil.hudson@iname.com> writes:
> Is there anything further I need to do to get the two patches I sent
> over the weekend merged (or constructively rejected)? They seem to have
> died a death.
They didn't. They are on my TODO list.
However, bumping them before two days is a bit short, at least on my
side. I suggest to wait a week before doing so. Hopefully, this will not
be necessary in this case. Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2016-05-09 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 9:34 Patches sent Phil Hudson
2016-05-09 10:11 ` Nicolas Goaziou [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3dbzgk6.fsf@saiph.selenimh \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=phil.hudson@iname.com \
/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/org-mode.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).