From: Ammar Faizi <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: Nugra <[email protected]>, Arthur Lapz <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: Re: [PATCH pit 1/3] lib: Remove unnecessary var_dump
Date: Sat, 26 Feb 2022 23:57:30 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/26/22 11:52 PM, Alviro Iskandar Setiawan wrote:
> The var_dump() in sendFile() is not needed. Maybe sir Ammar forgot
> to remove it when debugging :v
Ah yes, you're right. I forgot to remove the var_dump() here. It's
for debugging purpose only.
--
Ammar Faizi
next prev parent reply other threads:[~2022-02-26 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 16:52 [PATCH pit 0/3] Add Telegram Notification Support Alviro Iskandar Setiawan
2022-02-26 16:52 ` [PATCH pit 1/3] lib: Remove unnecessary var_dump Alviro Iskandar Setiawan
2022-02-26 16:57 ` Ammar Faizi [this message]
2022-02-26 16:52 ` [PATCH pit 2/3] bin/public-inbox-tg: Add Telegram CC notification support Alviro Iskandar Setiawan
2022-02-26 16:52 ` [PATCH pit 3/3] data: Add GNU/Weeb friends Alviro Iskandar Setiawan
2022-02-26 17:02 ` [PATCH pit 0/3] Add Telegram Notification Support Ammar Faizi
2022-02-26 17:11 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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