From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: acked
Date: Wed, 30 Oct 2013 17:20:07 +0000 [thread overview]
Message-ID: <20131030172007.GI16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20131030171544.GF26784@titan.lakedaemon.net>
On Wed, Oct 30, 2013 at 01:15:44PM -0400, Jason Cooper wrote:
> Gregory,
>
> I like the idea, and if you perhaps do '[PATCH X/Y] Acked' it should
> make it through the filters. (they currently whitelist 'GIT PULL' and
> 'PATCH' subjects).
>
> Sure would make things easier when going through the threads...
NAK. :)
The reason being that some mailing list archivers will break threads
with a subject line change, which will detach the "acked" from the
original messages.
If a patch made it though with "[PATCH" in the subject line, then a
reply (though *correctly* trimmed down as per Internet Etiquette
which is something people - including yourself as evidenced by the
message to which I'm replying - regularly don't do) will get through
without any issues.
next prev parent reply other threads:[~2013-10-30 17:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 16:55 [PATCH 0/2] Add support for OpenBlocks A7 Thomas Petazzoni
2013-10-30 16:55 ` [PATCH 1/2] ARM: kirkwood: add support for OpenBlocks A7 platform Thomas Petazzoni
2013-10-30 17:04 ` Andrew Lunn
2013-10-30 17:09 ` Gregory CLEMENT
[not found] ` <52713B10.9060809@free-electrons.com>
2013-10-30 17:15 ` acked Jason Cooper
2013-10-30 17:20 ` Russell King - ARM Linux [this message]
2013-10-30 17:26 ` acked Jason Cooper
2013-10-30 17:22 ` acked Gregory CLEMENT
2013-10-30 17:27 ` acked Jason Cooper
2013-10-30 19:57 ` [PATCH 1/2] ARM: kirkwood: add support for OpenBlocks A7 platform Jason Cooper
2013-10-31 8:37 ` Thomas Petazzoni
2013-10-31 9:17 ` Gregory CLEMENT
2013-10-31 9:21 ` Thomas Petazzoni
2013-10-31 12:50 ` Jason Cooper
2013-10-31 12:54 ` Gregory CLEMENT
2013-10-31 13:20 ` Jason Cooper
2013-10-30 16:55 ` [PATCH 2/2] ARM: kirkwood: enable HIGHMEM in defconfig Thomas Petazzoni
2013-10-30 17:00 ` Andrew Lunn
2013-10-30 17:09 ` Gregory CLEMENT
2013-11-01 15:35 ` Jason Cooper
-- strict thread matches above, loose matches on Subject: below --
2024-05-28 11:13 [PATCH 0/7] watchdog_reset cleanup Rasmus Villemoes
2024-05-29 7:35 ` Acked Angelo Dureghello
2024-06-19 21:27 [PATCH 1/7] m68k: Implement a default flush_dcache_all Tom Rini
2024-06-24 7:37 ` Acked Angelo Dureghello
2024-07-24 15:08 [PATCH 00/35] global_data: Reduce size of struct global_data Simon Glass
2024-07-24 15:08 ` [PATCH 01/35] global_data: Move pci_clk to m68k and powerpc Simon Glass
2024-07-29 7:57 ` Acked Angelo Dureghello
2024-09-26 20:44 [PATCH 00/27] led: Remove old status-LED code Simon Glass
2024-09-26 20:44 ` [PATCH 15/27] m68k: Drop unused status_led.h header file Simon Glass
2024-10-01 7:21 ` Acked Angelo Dureghello
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=20131030172007.GI16735@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.