From: Uladzislau Rezki <urezki@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Uladzislau Rezki (Sony)" <urezki@gmail.com>,
RCU <rcu@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
Feng Lee <379943137@qq.com>,
Neeraj upadhyay <Neeraj.Upadhyay@amd.com>,
Boqun Feng <boqun.feng@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Frederic Weisbecker <frederic@kernel.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [GIT PULL] RCU changes for v6.14
Date: Wed, 22 Jan 2025 12:28:00 +0100 [thread overview]
Message-ID: <Z5DWQHUxpUpwd7W-@pc636> (raw)
In-Reply-To: <CAHk-=wgGjEgK3V6XtGckJ5gdPsoj5Zn4O+ipN6Kvv83AKE2h9Q@mail.gmail.com>
On Tue, Jan 21, 2025 at 02:51:15PM -0800, Linus Torvalds wrote:
> On Fri, 17 Jan 2025 at 09:24, Uladzislau Rezki (Sony) <urezki@gmail.com> wrote:
> >
> > Please pull the latest RCU git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rcu/linux.git tags/rcu.release.v6.14
>
> Hmm. I have pulled this, and the resulting shortlog matches what you
> say I should have gotten.
>
> But your diffstat is odd and looks very wrong.
>
> Things like this:
>
> > tools/testing/selftests/bpf/map_tests/lpm_trie_map_basic_ops.c | 395 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> were already in my tree from before, and aren't new (and your shortlog
> doesn't mention them).
>
> Also, look at that line. It's long. It's not supposed to be that long.
> You've presumably generated this (incorrect) diffstat in a very wide
> terminal, and then cut-and-pasted that very wide output into the
> email.
>
> Please don't do that. Yes, git will default to wide output if the
> output is a wide terminal, but if you either pipe it into something
> else (may I suggest "xsel", so that it goes directly into your X
> clipboard).
>
> Or use "--stat=80" to limit the width manually to 80 columns.
>
> But the strange formatting is the less worrisome issue. The diffstat
> just being plain wrong is the more alarming thing.
>
Thank you for taking this in!
My script that generates a diff-stat is not perfect, i will fix it.
Sorry this is my bad.
--
Uladzislau Rezki
next prev parent reply other threads:[~2025-01-22 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 17:24 [GIT PULL] RCU changes for v6.14 Uladzislau Rezki (Sony)
2025-01-21 22:51 ` Linus Torvalds
2025-01-22 11:28 ` Uladzislau Rezki [this message]
2025-01-21 23:04 ` 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=Z5DWQHUxpUpwd7W-@pc636 \
--to=urezki@gmail.com \
--cc=379943137@qq.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksiy.avramchenko@sony.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--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