mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Petr Mladek <pmladek@suse.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL] tracing: Fix to recursion protection for 5.15
Date: Wed, 20 Oct 2021 18:12:41 -0400	[thread overview]
Message-ID: <20211020181241.0e6a2b47@gandalf.local.home> (raw)
In-Reply-To: <CAHk-=whr2M-jzyv9B8Co0V0TMvCpnH24fWYwxXrN9YeGKicoVw@mail.gmail.com>

On Wed, 20 Oct 2021 10:59:28 -1000
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Wed, Oct 20, 2021 at 6:17 AM Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > Oh, and I have a perl script that also adds "Cc"s. That could have done it
> > as well. :-/  
> 
> That sounds like the likely culprit.
> 
> I think doing a simple
> 
>    decode("MIME-Header", $cc)
> 
> should do it, but I'm not a perl person.

Well, that solves it from copying the header into the Cc list. But then I
have this error when running the git am:

error: cannot convert from US-ASCII to UTF-8
fatal: could not parse patch

But you are right. It's the copying of the header Cc list into the Cc list
of the commit that is causing my issue. Will investigate it more.

I probably could just stop doing that, as it also adds the Link: tag to the
lore email, which includes all the Cc's.

-- Steve

  reply	other threads:[~2021-10-20 22:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 13:13 Steven Rostedt
2021-10-20 16:10 ` Linus Torvalds
2021-10-20 16:17   ` Steven Rostedt
2021-10-20 20:59     ` Linus Torvalds
2021-10-20 22:12       ` Steven Rostedt [this message]
2021-10-20 22:41         ` Steven Rostedt
2021-10-21  6:08           ` Linus Torvalds
2021-10-21  6:16             ` Joe Perches
2021-10-21  6:27               ` Linus Torvalds
2021-10-21  6:36                 ` Joe Perches
2021-10-20 16:16 ` pr-tracker-bot

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=20211020181241.0e6a2b47@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®