From: Linus Torvalds <torvalds@linux-foundation.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Jin Yao <yao.jin@linux.intel.com>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
John Garry <john.garry@huawei.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [GIT PULL] perf tools fixes for v5.11, 2nd batch
Date: Fri, 22 Jan 2021 13:59:02 -0800 [thread overview]
Message-ID: <CAHk-=wjXjWWwOtGv22Edx+hv1od3g_eR+68J+bS93GiKqok15w@mail.gmail.com> (raw)
In-Reply-To: <20210122135156.608434-1-acme@kernel.org>
On Fri, Jan 22, 2021 at 5:52 AM Arnaldo Carvalho de Melo
<acme@kernel.org> wrote:
>
> Test results in the signed tag at:
Side note: I'd actually prefer if you didn't do this. These big things
end up being (a hidden) part of the merge commit (and that's how the
tag verification works after-the-fact: ie I don't just verify the tag
when I pull, you can also do the verification later), and it really
makes zero sense to add 28kB of data to each merge just because you
hid them in the signed tag.
It would actually be better to have it just in the email at the end,
not in the tag.
Please?
Linus
next prev parent reply other threads:[~2021-01-22 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 13:51 [GIT PULL] perf tools fixes for v5.11, 2nd batch Arnaldo Carvalho de Melo
2021-01-22 21:59 ` Linus Torvalds [this message]
2021-01-25 16:39 ` Arnaldo Carvalho de Melo
2021-01-22 22:00 ` 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='CAHk-=wjXjWWwOtGv22Edx+hv1od3g_eR+68J+bS93GiKqok15w@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=john.garry@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=qiangqing.zhang@nxp.com \
--cc=tglx@linutronix.de \
--cc=yao.jin@linux.intel.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 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).