From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Jani Nikula <jani@nikula.org>, Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH 2/2] emacs: new mua mailto: URI handler
Date: Sat, 14 Apr 2012 13:36:04 -0700 [thread overview]
Message-ID: <87bomucaq3.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87wr5idprb.fsf@nikula.org>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Sat, Apr 14 2012, Jani Nikula <jani@nikula.org> wrote:
> I'm going through the review queue right now, tagging notmuch::stale any
> patches that don't apply on master. I was just about to nmbug push stale
> on this one (2/2). Is that in error? Care to verify?
Yes, it is an error. This patch applies to master. Did you in fact
verify that it doesn't? You should not be tagging patches stale if they
in fact still apply to master. If they still need review or something
else that's a different matter. Please don't mark things as stale if
they are not.
Obviously I still care about this patch, or I wouldn't have re-commented
on it.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2012-04-14 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 19:33 [PATCH 1/2] test: emacs mailto: URI handling Jameson Graef Rollins
2012-01-29 19:33 ` [PATCH 2/2] emacs: new mua mailto: URI handler Jameson Graef Rollins
2012-01-30 15:43 ` David Edmondson
2012-01-30 17:36 ` Jameson Graef Rollins
2012-04-14 20:05 ` Jameson Graef Rollins
2012-04-14 20:26 ` Jani Nikula
2012-04-14 20:36 ` Jameson Graef Rollins [this message]
2012-04-14 21:22 ` Jani Nikula
2012-04-14 21:26 ` Jameson Graef Rollins
2012-04-14 21:56 ` Jani Nikula
2012-04-14 21:27 ` [PATCH v2 " Jameson Graef Rollins
2012-06-19 7:42 ` Mark Walters
2012-06-19 20:46 ` Jameson Graef Rollins
2012-10-15 17:12 ` [PATCH 1/2] test: emacs mailto: URI handling Ethan Glasser-Camp
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bomucaq3.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).