From: Ahmad Gani <reyuki@gnuweeb.org>
To: Ammar Faizi <ammarfaizi2@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: Mon, 15 Sep 2025 00:44:31 +0700 [thread overview]
Message-ID: <CAADvAgq-djmp8zac+Lr0NyU4uEOd55rq8u+ntbUQoVih93XvJw@mail.gmail.com> (raw)
In-Reply-To: <20250914121633.GA774647-ammarfaizi2@gnuweeb.org>
On Sun, Sep 14, 2025 at 7:16 PM Ammar Faizi wrote:
> 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?
Well, I think to reduce the code size, but after a second thought if
using too many #ifdef is considered bad, then I just need to delete it.
> 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?
Err... sorry, it seems I was too hasty in preparing this patchset and
forgot about this....
> Please stop vibe-coding.
The only code that's written by AI is enum and struct in dnsparser.h and
that's also because at that time you say it's more effective to do so
than manually (I agree with this).
But if your definition of vibe-coding is to code without paying attention
to what you write, then you might be right.
My seriousness depends on whether I enjoyed the activity or not, and I
enjoy the first time I learn and understand about new things but now I
wonder why I'm not as excited as the first time I experienced it.
I need to find a way to restore this feeling.
--
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
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 [this message]
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=CAADvAgq-djmp8zac+Lr0NyU4uEOd55rq8u+ntbUQoVih93XvJw@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