From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Matthew Wilcox <willy@infradead.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Livepatching <live-patching@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Attreyee Mukherjee <tintinm2017@gmail.com>,
Chandan Babu R <chandanbabu@kernel.org>
Subject: Re: [PATCH 0/2] Minor grammatical fixup for livepatch docs
Date: Thu, 30 Nov 2023 07:13:02 +0700 [thread overview]
Message-ID: <ZWfTjmL9RCUrqCqj@archie.me> (raw)
In-Reply-To: <ZWdYGrhTYFzG5BZq@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Wed, Nov 29, 2023 at 03:26:18PM +0000, Matthew Wilcox wrote:
> On Wed, Nov 29, 2023 at 07:29:35AM -0700, Jonathan Corbet wrote:
> > Bagas Sanjaya <bagasdotme@gmail.com> writes:
> >
> > > I was prompted to write this little grammar fix series when reading
> > > the fix from Attreyee [1], with review comments requesting changes
> > > to that fix. So here's my version of the fix, with reviews from [1]
> > > addressed (and distinct grammar fixes splitted).
> >
> > How is this helpful? Why are you trying to push aside somebody who is
> > working toward a first contribution to the kernel? This is not the way
> > to help somebody learn to work with the kernel community.
>
> This is not the first such "contribution" from Bagas recently.
>
> https://lore.kernel.org/linux-doc/20231121095658.28254-1-bagasdotme@gmail.com/
>
> was as a result of
> https://lore.kernel.org/linux-xfs/87r0klg8wl.fsf@debian-BULLSEYE-live-builder-AMD64/
>
> I didn't say anything at the time, but clearly I should have squelched
> this bad behaviour by Bagas before he did it to a newbie.
>
> Bagas, find your own project to work on. Don't steal glory from others.
OK, thanks! I was in 'gabut mode' then...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-30 0:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 13:25 [PATCH 0/2] Minor grammatical fixup for livepatch docs Bagas Sanjaya
2023-11-29 13:25 ` [PATCH 1/2] Documentation: livepatch: Correct "step on each other's toes" idiom Bagas Sanjaya
2023-11-29 13:25 ` [PATCH 2/2] Documentation: livepatch: Correct opposite of releasing locks Bagas Sanjaya
2023-11-29 13:53 ` [PATCH 0/2] Minor grammatical fixup for livepatch docs Joe Lawrence
2023-11-29 23:58 ` Bagas Sanjaya
2023-11-30 0:08 ` Matthew Wilcox
2023-11-30 3:25 ` Bagas Sanjaya
2023-11-30 0:10 ` Jonathan Corbet
2023-11-30 8:04 ` Bagas Sanjaya
2023-11-29 14:29 ` Jonathan Corbet
2023-11-29 15:26 ` Matthew Wilcox
2023-11-30 0:13 ` Bagas Sanjaya [this message]
[not found] ` <CAJjsb4r5S80ZqdX3EnucSfeiyeFEgUOW+5++=XG4rT85Os4PNQ@mail.gmail.com>
2023-11-30 0:14 ` Bagas Sanjaya
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=ZWfTjmL9RCUrqCqj@archie.me \
--to=bagasdotme@gmail.com \
--cc=chandanbabu@kernel.org \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=tintinm2017@gmail.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).