From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] [PATCH] Distinguish between \e and \i.
Date: Fri, 28 Jan 2011 11:40:10 +0000 [thread overview]
Message-ID: <20110128114010.6bb4e27b@snowcone> (raw)
In-Reply-To: <19778.35806.305392.305552@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Fri, 28 Jan 2011 10:26:54 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:
> A more general question, should such patches that do not change the
> meaning of the text be sent to this list for review?
I'd be inclined to say yes, unless it's something that's so amazingly
obvious that it couldn't possibly be wrong.
A lack of responses to trivial patch emails doesn't mean they're being
ignored. It just means no-one's got anything to say about them, but
doesn't think the patch is controversial enough to warrant a "looks
good to me".
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-01-28 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 9:26 [gentoo-pms] [PATCH] Distinguish between \e and \i Ulrich Mueller
2011-01-28 11:40 ` Ciaran McCreesh [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=20110128114010.6bb4e27b@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-pms@lists.gentoo.org \
--cc=ulm@gentoo.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