From: Ahmad Gani <reyuki@gnuweeb.org>
To: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
"GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v11 6/6] gwproxy: Reduce #ifdef CONFIG_RAW_DNS
Date: Mon, 15 Sep 2025 00:45:05 +0700 [thread overview]
Message-ID: <CAADvAgpe_svjk1r9ewdeQKHT-=S1K4uvgHU9uEjoMdnc3U5LDQ@mail.gmail.com> (raw)
In-Reply-To: <CAOG64qO=+AQUu-7rqC0X=rnb1GcPZTg55tnDxgasn_q6s07A6A@mail.gmail.com>
On Sun, Sep 14, 2025 at 9:26 PM Alviro Iskandar Setiawan wrote:
> On Sun, Sep 14, 2025 at 7:16 PM Ammar Faizi wrote:
> > Please stop vibe-coding.
>
> Oh, that explains why he keeps making the same mistake even if we told
> him multiple times not to. It seems the AI he used is not smart enough
> to do C programming.
Since the rise of AI-stuff, It's easy to jump to conclusions these days.
People started to correlate all things to it, as if all explanations
could magically be hidden under the word AI.
You know what maomao said? stop conjecturing. /j
> Ahmad Gani, did you really use AI to write patches?
I often worry about my grammar and fluency in English, so I used AI to
fix that. Not to generate completely new words, but to polish my sentences.
> When you get comments on code review, please address those properly.
> Avoid repeating the same mistake too many times.
>
> It happens once, fine, it happens twice, still fine, it happens for
> the third times, something is wrong with you. Moreover the mistake you
> did just get warned recently.
People make mistakes, multiple times? yeah that's not normal, but
abnormal people do exist in this world.and I hope you can accept these
kinds of people and not give up on guiding them.
Anyway, I accept the criticism and will try to put more thought before
sending the next patchset.
--
Ahmad Gani
next prev parent reply other threads:[~2025-09-14 17:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 5:09 [PATCH gwproxy v11 0/6] Initial work on integration of DNS parser lib in gwproxy Ahmad Gani
2025-09-14 5:09 ` [PATCH gwproxy v11 1/6] dns: Use __sys_close instead of close Ahmad Gani
2025-09-14 5:09 ` [PATCH gwproxy v11 2/6] gwproxy: Define __maybe_unused macro Ahmad Gani
2025-09-14 5:09 ` [PATCH gwproxy v11 3/6] dnsparser: Add dns parser code Ahmad Gani
2025-09-14 5:09 ` [PATCH gwproxy v11 4/6] gwproxy: Refactor code base to add experimental raw DNS backend Ahmad Gani
2025-09-14 12:14 ` Ammar Faizi
2025-09-14 13:54 ` Alviro Iskandar Setiawan
2025-09-14 17:46 ` Ahmad Gani
2025-09-14 5:09 ` [PATCH gwproxy v11 5/6] gwproxy: Update Makefile and configure scripts Ahmad Gani
2025-09-14 12:55 ` Ammar Faizi
2025-09-14 17:45 ` Ahmad Gani
2025-09-14 5:09 ` [PATCH gwproxy v11 6/6] gwproxy: Reduce #ifdef CONFIG_RAW_DNS Ahmad Gani
2025-09-14 12:16 ` Ammar Faizi
2025-09-14 14:26 ` Alviro Iskandar Setiawan
2025-09-14 17:45 ` Ahmad Gani [this message]
2025-09-14 17:59 ` Alviro Iskandar Setiawan
2025-09-14 18:13 ` Ahmad Gani
2025-09-15 2:21 ` Alviro Iskandar Setiawan
2025-09-14 17:44 ` Ahmad Gani
2025-09-14 19:02 ` Ammar Faizi
2025-09-15 2:50 ` Alviro Iskandar Setiawan
2025-09-14 12:51 ` (subset) [PATCH gwproxy v11 0/6] Initial work on integration of DNS parser lib in gwproxy Ammar Faizi
2025-09-14 17:22 ` Alviro Iskandar Setiawan
2025-09-14 18:07 ` Ahmad Gani
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='CAADvAgpe_svjk1r9ewdeQKHT-=S1K4uvgHU9uEjoMdnc3U5LDQ@mail.gmail.com' \
--to=reyuki@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.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