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 v6 00/11] Initial work on integration of DNS parser lib in gwproxy
Date: Fri, 29 Aug 2025 05:23:03 +0700 [thread overview]
Message-ID: <20250828222303.GA540452-ammarfaizi2@gnuweeb.org> (raw)
In-Reply-To: <20250828143444.540247-1-reyuki@gnuweeb.org>
On Thu, Aug 28, 2025 at 09:34:22PM +0700, Ahmad Gani wrote:
> Ahmad Gani (11):
> gwproxy: Fix syntax error inside assertion
> gwproxy: Fix socks5 failure on debug mode
> dnsparser: Add dns parser code
> dnsparser: remove unused constant
> dnsparser: Ignore CNAME if any
> dns: Remove code block related to the usage of glibc's getaddrinfo_a
> function
> dns: refactor dns.c to integrate the dns parser
> dns: revert removed DNS code and disable raw DNS by default
> test: revert DNS test-case
> gwproxy: Add DNS server option
> dns: Add fallback mechanism for raw DNS
Stop doing the same mistake again, again, and again. Don't send a patch
to fix your previous patch. I'll add unnecessary noise for the reviewers
and clutter the git history.
For example:
- You add various enums in patch #3, but you remove them in patch #4.
- You remove getaddrinfo_a() in patch #6, but you add it again in patch #8.
- You remove the DNS tests in patch #6, but your bring the tests back
in patch #9.
There are more patterns like that. Something like that should just
be f*ck*ng squashed. No need to bomb the list and reviewers with
unnecessary additions and removals which end up doing nothing because
your addtions are fully undone by your removals and vice-versa.
You should only send fix-and-revert patches to fix upstream commits,
not to fix your local commits.
--
Ammar Faizi
next prev parent reply other threads:[~2025-08-28 22:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 14:34 [PATCH gwproxy v6 00/11] Initial work on integration of DNS parser lib in gwproxy Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 01/11] gwproxy: Fix syntax error inside assertion Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 02/11] gwproxy: Fix socks5 failure on debug mode Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 03/11] dnsparser: Add dns parser code Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 04/11] dnsparser: remove unused constant Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 05/11] dnsparser: Ignore CNAME if any Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 06/11] dns: Remove code block related to the usage of glibc's getaddrinfo_a function Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 07/11] dns: refactor dns.c to integrate the dns parser Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 08/11] dns: revert removed DNS code and disable raw DNS by default Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 09/11] test: revert DNS test-case Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 10/11] gwproxy: Add DNS server option Ahmad Gani
2025-08-28 14:34 ` [PATCH gwproxy v6 11/11] dns: Add fallback mechanism for raw DNS Ahmad Gani
2025-08-28 21:52 ` [PATCH gwproxy v6 00/11] Initial work on integration of DNS parser lib in gwproxy Ammar Faizi
2025-08-28 22:23 ` Ammar Faizi [this message]
2025-08-29 0:54 ` Ahmad Gani
2025-08-29 1:59 ` 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=20250828222303.GA540452-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