live-patching.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
	Joe Lawrence <joe.lawrence@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Livepatching <live-patching@vger.kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
	Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
	Petr Mladek <pmladek@suse.com>,
	Attreyee Mukherjee <tintinm2017@gmail.com>
Subject: Re: [PATCH 0/2] Minor grammatical fixup for livepatch docs
Date: Thu, 30 Nov 2023 15:04:38 +0700	[thread overview]
Message-ID: <ZWhCFic541YaYf4w@archie.me> (raw)
In-Reply-To: <87h6l4ksni.fsf@meer.lwn.net>

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

On Wed, Nov 29, 2023 at 05:10:25PM -0700, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
> 
> > On 11/29/23 20:53, Joe Lawrence wrote:
> >> On 11/29/23 08:25, Bagas Sanjaya wrote:
> >>> 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).
> >>>
> >> 
> >> Typical kernel workflow would be for Attreyee to incorporate feedback
> >> and post their v2 after a day or two.  From the format they posted, it
> >> appears to be a first(ish) kernel contribution post.  Let's be kind and
> >> patient so they we all may benefit from the practice of iterating on
> >> their patch.
> >> 
> >
> > I do this posting because I thought the OP (Attreyee) didn't respond in
> > timely manner (just like random Chinese contributors like @cdjrlc.com
> > and @208suo.com people).
> 
> Seriously?  The original post was on Monday, yours came less than 48
> hours later.  Not only can we not expect that kind of rapid turnaround
> from anybody, but we actively discourage rapid resending of patches.
> Rather than dig yourself in deeper, I suggest you simply apologize to
> the original poster and find something more useful to do.

Done, thanks!

And yes, I'm also focusing on regression tracking and Bugzilla
triaging.

Ciao, Bagas.

-- 
An old man doll... just what I always wanted! - Clara

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

  reply	other threads:[~2023-11-30  8:04 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 [this message]
2023-11-29 14:29 ` Jonathan Corbet
2023-11-29 15:26   ` Matthew Wilcox
2023-11-30  0:13     ` Bagas Sanjaya
     [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=ZWhCFic541YaYf4w@archie.me \
    --to=bagasdotme@gmail.com \
    --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 \
    /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).