[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZxocelppgHf8D9vk@archie.me>
Date: Thu, 24 Oct 2024 17:07:54 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Jonathan Corbet <corbet@....net>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
anish kumar <yesanishhere@...il.com>
Cc: perex@...ex.cz, tiwai@...e.com, linux-sound@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] Docs/sound: Update codec-to-codec documentation
On Wed, Oct 23, 2024 at 10:15:08AM -0600, Jonathan Corbet wrote:
> Charles Keepax <ckeepax@...nsource.cirrus.com> writes:
>
> > On Sun, Oct 20, 2024 at 09:37:06AM -0700, anish kumar wrote:
> >> Updated documentation to provide more details
> >> for codec-to-codec connection.
> >>
> >> Signed-off-by: anish kumar <yesanishhere@...il.com>
> >> ---
> >
> > The patch doesn't seem to apply cleanly for me, my system doesn't
> > seem to like:
> >
> > Content-Type: text/plain; charset="y"
> >
> > Not sure if that is a problem on my end or yours, but I am not
> > familiar with that encoding.
>
> That's something that "git send-email" does occasionally. At some point
> I remember that somebody figured out why that was, but it escapes me
> now...
AFAIK in this case, when sending patches with non-ASCII characters in them,
git-send-email(1) will try figuring out the encoding, which will often
assumed to be UTF-8. You can simply hit Enter when it asks the correct
encoding.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists