public inbox for [email protected]
 help / color / mirror / Atom feed
From: Arthur Lapz <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>
Subject: Re: [PATCH] slc: Fix file descriptor leak
Date: Mon, 06 Jun 2022 09:59:17 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Mon, 2022-06-06 at 09:57 +0700, Ammar Faizi wrote:
> On 6/6/22 9:56 AM, Arthur Lapz wrote:
> > > How did you test this?
> > I did nothing.
> > 
> > I guess it worked because you have restarted the `slc server`
> 
> Yes, I have just restarted the SLC server. Do you have another
> issue now?
> 
I don't have.
Thanks :3
-- 
Arthur Lapz

  reply	other threads:[~2022-06-06  2:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06  2:27 [PATCH] slc: Fix file descriptor leak Ammar Faizi
2022-06-06  2:28 ` Ammar Faizi
2022-06-06  2:42   ` Arthur Lapz
2022-06-06  2:46     ` Ammar Faizi
2022-06-06  2:51       ` Ammar Faizi
2022-06-06  2:56         ` Arthur Lapz
2022-06-06  2:57           ` Ammar Faizi
2022-06-06  2:59             ` Arthur Lapz [this message]
2022-06-06  2:54 ` Alviro Iskandar Setiawan
2022-06-06  3:02   ` 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=adb5af3856daf645c18323643d0183ba2c343eef.camel@gnuweeb.org \
    [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