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 v6 00/11] Initial work on integration of DNS parser lib in gwproxy
Date: Fri, 29 Aug 2025 07:54:40 +0700 [thread overview]
Message-ID: <CAADvAgoU=Y3prk7mt51o2w69memLrq_1uMx9XcawUZiPiLx0yA@mail.gmail.com> (raw)
In-Reply-To: <20250828222303.GA540452-ammarfaizi2@gnuweeb.org>
On Fri, Aug 29, 2025 at 5:23 AM Ammar Faizi wrote:
> 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.
Sorry, I should have clarified and explained it better.
I meant to provide more context and to open a discussion about each commit
in this patch series, not to have the patches applied as-is. But I guess
you're right; if I want to do that I can point to the branch on the GitHub
repository and send a cleaned set of patches.
Now that I understand patch series are intended to be applied, and that
unnecessary context just becomes noise for people who didn't make these
modifications, I will send a cleaned patch series next time.
--
Ahmad Gani
next prev parent reply other threads:[~2025-08-29 0:55 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
2025-08-29 0:54 ` Ahmad Gani [this message]
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='CAADvAgoU=Y3prk7mt51o2w69memLrq_1uMx9XcawUZiPiLx0yA@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