GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Alviro Iskandar Setiawan <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Muhammad Rizki <[email protected]>,
	"GNU/Weeb Mailing List" <[email protected]>
Subject: Re: [PATCH v2 0/3] New Discord bot and full refactor scripts
Date: Sat, 3 Sep 2022 17:06:57 +0700	[thread overview]
Message-ID: <CAOG64qP7H05iDnuOR3MyL_KWA9dH5cODCejhSq6-ZD_F5EtJig@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>

On Sat, Sep 3, 2022 at 4:58 PM Ammar Faizi wrote:
> On 9/3/22 4:56 PM, Alviro Iskandar Setiawan wrote:
>> On Sat, Sep 3, 2022 at 8:28 AM Ammar Faizi wrote:
>>> On 8/27/22 10:02 AM, Muhammad Rizki wrote:
>>>> Muhammad Rizki (3):
>>>>     Move the Telegram bot source code
>>>>     First release Discord bot
>>>>     Full refactor bot scripts
>>>
>>> Please split these into smaller manageable-reviewable pieces.
>>> I simply can't review it. Each patch should only do one thing.
>>
>> you may want to impose stricter standards for this workflow, otherwise
>> it's not going to be productive, especially Rizki isn't that
>> experienced with this emailed patchset procedure. You should also
>> consider giving him a pay rise if you do more a complex workflow like
>> this
>
> We certainly can do that. But let's see how this is going to be done
> in the next revision. If it's starting to get better, I will reconsider.

ic ic,

i also want to file a complaint, you didn't give enough attention to
him. This makes the work boring, thus the result isn't good

tq

-- Viro

  reply	other threads:[~2022-09-03 10:07 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27  3:02 [PATCH v2 0/3] New Discord bot and full refactor scripts Muhammad Rizki
2022-08-27  3:02 ` [PATCH v2 1/3] Move the Telegram bot source code Muhammad Rizki
2022-08-27  3:02 ` [PATCH v2 2/3] First release Discord bot Muhammad Rizki
2022-09-03  0:29   ` Ammar Faizi
2022-08-27  3:02 ` [PATCH v2 3/3] Full refactor bot scripts Muhammad Rizki
2022-08-27 10:40 ` [PATCH v2 0/3] New Discord bot and full refactor scripts Ammar Faizi
2022-08-27 16:00   ` Muhammad Rizki
2022-08-29  3:39     ` Ammar Faizi
2022-09-03  0:42     ` Ammar Faizi
2022-09-03  0:45       ` Ammar Faizi
2022-09-03  1:01         ` Muhammad Rizki
2022-09-03  9:44           ` Ammar Faizi
2022-09-03  9:46             ` Ammar Faizi
2022-09-03 10:05             ` Muhammad Rizki
2022-09-03 10:32               ` Ammar Faizi
2022-09-03 10:34                 ` Ammar Faizi
2022-09-03 10:40                   ` Ammar Faizi
2022-09-03 10:58                     ` Muhammad Rizki
2022-09-03 10:52                   ` Muhammad Rizki
2022-09-03 10:43                 ` Muhammad Rizki
2022-09-03  0:56       ` Muhammad Rizki
2022-09-03  1:00         ` Ammar Faizi
2022-09-03  0:29 ` Ammar Faizi
2022-09-03  1:28 ` Ammar Faizi
2022-09-03  3:09   ` Muhammad Rizki
2022-09-03  9:56   ` Alviro Iskandar Setiawan
2022-09-03  9:58     ` Ammar Faizi
2022-09-03 10:06       ` Alviro Iskandar Setiawan [this message]
2022-09-03 10:12         ` Ammar Faizi
2022-09-03 10:43           ` Alviro Iskandar Setiawan
2022-09-03 11:09             ` Ammar Faizi

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=CAOG64qP7H05iDnuOR3MyL_KWA9dH5cODCejhSq6-ZD_F5EtJig@mail.gmail.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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