All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
	Charles Keepax <ckeepax@opensource.cirrus.com>,
	anish kumar <yesanishhere@gmail.com>
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Docs/sound: Update codec-to-codec documentation
Date: Thu, 24 Oct 2024 17:07:54 +0700	[thread overview]
Message-ID: <ZxocelppgHf8D9vk@archie.me> (raw)
In-Reply-To: <87sesmn6cz.fsf@trenco.lwn.net>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

On Wed, Oct 23, 2024 at 10:15:08AM -0600, Jonathan Corbet wrote:
> Charles Keepax <ckeepax@opensource.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@gmail.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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-10-24 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-20 16:37 [PATCH v2] Docs/sound: Update codec-to-codec documentation anish kumar
2024-10-23 16:10 ` Charles Keepax
2024-10-23 16:15   ` Jonathan Corbet
2024-10-24 10:07     ` Bagas Sanjaya [this message]
2024-10-24 20:27   ` anish kumar
2024-10-25  8:58     ` Charles Keepax
2024-10-26 21:52       ` anish kumar

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=ZxocelppgHf8D9vk@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=yesanishhere@gmail.com \
    /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.