From: Andrew Eikum <aeikum@codeweavers.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andrew Eikum <aeikum@codeweavers.com>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [alsa-plugins PATCH] pulse: Support 24-bit formats
Date: Mon, 20 Aug 2012 07:42:05 -0500 [thread overview]
Message-ID: <20120820124204.GW2424@foghorn.codeweavers.com> (raw)
In-Reply-To: <s5hd32lrjui.wl%tiwai@suse.de>
On Mon, Aug 20, 2012 at 11:30:45AM +0200, Takashi Iwai wrote:
> At Fri, 17 Aug 2012 15:41:07 -0500,
> Andrew Eikum wrote:
> > These formats were introduced in PulseAudio 0.9.15. There aren't any
> > new formats supported since then, so this also brings the PulseAudio
> > plugin in sync with current PulseAudio.
> >
> > Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
> > ---
> >
> > There was a problem once before with a patch I submitted. This is
> > using format-patch and imap-send, so hopefully it goes through better
> > than it did before :)
>
> Well, unfortunately it's not a preferred form of the patch.
> The patch commit log must be embedded in the patch itself. That is,
> the text above including your sign-off must be in the git commit log,
> then generate the patch via git-format-patch or git show --pretty=email.
>
> In anyway, I applied your patch manually now.
> Please try the right way at the next time.
>
I guess I'm used to how the Git project and the Wine maintainer do it.
They import the entire mbox file with 'git am'. This works properly
for the mail I sent, including putting the message and S-o-b line into
the commit log and ignoring the bit between the --- and the patch.
I'll make sure the attachment itself contains all of those details
next time.
Thanks for applying,
Andrew
next prev parent reply other threads:[~2012-08-20 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 20:41 [alsa-plugins PATCH] pulse: Support 24-bit formats Andrew Eikum
2012-08-20 9:30 ` Takashi Iwai
2012-08-20 12:42 ` Andrew Eikum [this message]
2012-08-20 12:56 ` Takashi Iwai
2012-08-20 13:04 ` Andrew Eikum
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=20120820124204.GW2424@foghorn.codeweavers.com \
--to=aeikum@codeweavers.com \
--cc=alsa-devel@alsa-project.org \
--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).