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 v7 0/2] Initial work on integration of DNS parser lib in gwproxy
Date: Fri, 29 Aug 2025 15:06:17 +0700 [thread overview]
Message-ID: <CAADvAgoJUMhnjn2GhvzauKYLizHDvH8GmTL2O+DCWC-gH--FJw@mail.gmail.com> (raw)
In-Reply-To: <CAFBCWQL8uJGBfAkuMh-o_1GWpBt6JEAoQ0BN+dkwWLgm_qU4VQ@mail.gmail.com>
On Fri, Aug 29, 2025 at 3:00 PM Ammar Faizi wrote:
> On Fri, Aug 29, 2025 at 2:52 PM Ahmad Gani wrote:
> > It detects trailing space from other files too, but I guess it's fine as
> > it's not part of the patchset.
>
> It would be great if you could send one patch to clean all trailing
> whitespaces for all files in src/gwproxy/. Commits introducing those
> trailing whitespaces did not go via git-format-patch and git-am, so
> they were not caught and did not cause errors
Well, I don't mind cleaning it up, I will send the patch shortly.
--
Ahmad Gani
prev parent reply other threads:[~2025-08-29 8:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 3:36 [PATCH gwproxy v7 0/2] Initial work on integration of DNS parser lib in gwproxy Ahmad Gani
2025-08-29 3:36 ` [PATCH gwproxy v7 1/2] dnsparser: Add dns parser code Ahmad Gani
2025-08-29 4:39 ` Ammar Faizi
2025-08-29 3:36 ` [PATCH gwproxy v7 2/2] gwproxy: refactor code base to add experimental raw DNS backend Ahmad Gani
2025-08-29 4:36 ` Ammar Faizi
2025-08-29 7:35 ` Ahmad Gani
2025-08-29 7:39 ` Ammar Faizi
2025-08-29 4:36 ` [PATCH gwproxy v7 0/2] Initial work on integration of DNS parser lib in gwproxy Ammar Faizi
2025-08-29 6:57 ` Ahmad Gani
2025-08-29 7:22 ` Ammar Faizi
2025-08-29 7:30 ` Ammar Faizi
2025-08-29 7:39 ` Ahmad Gani
2025-08-29 7:45 ` Ammar Faizi
2025-08-29 7:36 ` Ammar Faizi
2025-08-29 7:51 ` Ahmad Gani
2025-08-29 8:00 ` Ammar Faizi
2025-08-29 8:06 ` Ahmad Gani [this message]
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=CAADvAgoJUMhnjn2GhvzauKYLizHDvH8GmTL2O+DCWC-gH--FJw@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