From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Timur Tabi <timur@freescale.com>,
perex@perex.cz, tiwai@suse.de, lrg@ti.com,
linux-next@vger.kernel.org
Subject: Re: [PATCH] sound: fix trivial build error in mpc5200_dma.c
Date: Tue, 28 Feb 2012 10:27:29 +0000 [thread overview]
Message-ID: <20120228102728.GB3121@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAP=VYLrdAqUrn0WERvbM_JqVSPWxU94ZJkF7C0HaJysy6fCy7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
On Mon, Feb 27, 2012 at 07:43:20PM -0500, Paul Gortmaker wrote:
> On Mon, Feb 27, 2012 at 6:56 PM, Mark Brown
> > The first line of the changelog which gets treated specially in various
> > ways.
> Automated scripts? Something else? I'd be interested to know.
Things that use log summaries like git send-email and request-pull which
pick out the first line of the changelog and do something different with
it.
> I have to admit being confused by this as well. I paged through the
> git whatchanged info, and guessed that I should have used a prefix
> like "ASoC: mpc5200_dma" (camelcase sic) but I think that to expect
> that level of awareness from general contributors is probably expecting
> a bit much. I like to think I'm not totally clueless, but I would have
> never thought of the above in advance...
Well, most people seem to manage to get it right (I expect on the basis
that they write a log which looks like the other logs for the code). If
you're thinking far enough to put a subsystem prefix on the commit log
in the first place it seems reasonable to expect one that's in use
rather than just creating one.
> In any case, if I have further fixups I happen across, I will try to feed
> your bots the correct prefix.
It's nothing custom on my side, I only use the vanilla git porcelain
(though I do do things like grepping mailing lists visually so when
things aren't CCed properly I'm less likely to notice the mailing list
version of them). I'd expect there are people with subject line based
filters, though - patchwork might care for example.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-02-28 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 21:12 [PATCH] sound: fix trivial build error in mpc5200_dma.c Paul Gortmaker
2012-02-27 14:59 ` Mark Brown
2012-02-27 21:56 ` Timur Tabi
2012-02-27 23:56 ` Mark Brown
2012-02-28 0:43 ` Paul Gortmaker
2012-02-28 10:27 ` Mark Brown [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=20120228102728.GB3121@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=paul.gortmaker@windriver.com \
--cc=perex@perex.cz \
--cc=timur@freescale.com \
--cc=tiwai@suse.de \
/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).