From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Ahmad Gani <reyuki@gnuweeb.org>
Cc: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v11 6/6] gwproxy: Reduce #ifdef CONFIG_RAW_DNS
Date: Sun, 14 Sep 2025 19:16:33 +0700 [thread overview]
Message-ID: <20250914121633.GA774647-ammarfaizi2@gnuweeb.org> (raw)
In-Reply-To: <20250914050943.184934-7-reyuki@gnuweeb.org>
On Sun, Sep 14, 2025 at 12:09:40PM +0700, Ahmad Gani wrote:
> No need to wrap struct members in #ifdef, adding a couple of bytes isn't
> a big deal.
Then why did you add it in the first place?
Again, don't add a patch to undo your previous patch. Something like
this should just be squashed. How many times more should I tell you
this again?
Please stop vibe-coding.
I have been observing your patch submissions since July and I saw
various characters that don't actually exist on keyboard in your commit.
And I believe it's a very clear indication that it was not written via
a keyboard, but copy-pasted from somewhere else, likely AIs.
I did not have problems with your prior patches, but your habbit being
driven by AIs in writing patches is not actually healthy down the road.
Especially, when you're working on more complex things like this, the
result is horribly ridiculous.
It's fine to use AI, but it's not fine to let AI dominate your work.
--
Ammar Faizi
next prev parent reply other threads:[~2025-09-14 12:16 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 [this message]
2025-09-14 14:26 ` Alviro Iskandar Setiawan
2025-09-14 17:45 ` Ahmad Gani
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=20250914121633.GA774647-ammarfaizi2@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=reyuki@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