Tea Inside Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Alviro Iskandar Setiawan <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Tea Inside Mailing List <[email protected]>
Subject: Re: [PATCH teavpn2 0/5] Update README, Refactor and Fix Config Template
Date: Sat, 22 Jan 2022 12:44:21 +0700	[thread overview]
Message-ID: <CAOG64qP[email protected]> (raw)
In-Reply-To: <[email protected]>

On Sat, Jan 22, 2022 at 12:41 PM Ammar Faizi <[email protected]> wrote:
> On 1/22/22 12:14 PM, Ammar Faizi wrote:
> > On Sat, Jan 22, 2022 at 12:06 PM Alviro Iskandar Setiawan wrote:
> >>
> >> Hello sir,
> >> There are 5 patces in this series. 2 pathces for updating README.md file,
> >> 1 patch for refactor mutex helpers, 2 patches for fixing config template.
> >>
> >
> > Applied, thanks!
> >
>
> BTW Viro, regarding the GUI support. Who will continue it? Are you still
> progressing on this one?

i'm not sure sir, but khaerul was working on the config editor
https://t.me/TeaInside/48193

  reply	other threads:[~2022-01-22  5:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22  5:06 [PATCH teavpn2 0/5] Update README, Refactor and Fix Config Template Alviro Iskandar Setiawan
2022-01-22  5:06 ` [PATCH teavpn2 1/5] README: Remove RELEASE_MODE var Alviro Iskandar Setiawan
2022-01-22  5:06 ` [PATCH teavpn2 2/5] README: Add instruction to build with GUI Alviro Iskandar Setiawan
2022-01-22  5:06 ` [PATCH teavpn2 3/5] mutex: Refactor mutex helpers Alviro Iskandar Setiawan
2022-01-22  5:06 ` [PATCH teavpn2 4/5] config/client: Fix data_dir for client config template Alviro Iskandar Setiawan
2022-01-22  5:06 ` [PATCH teavpn2 5/5] config/{client,server}: Update interface name to teavpn2 Alviro Iskandar Setiawan
2022-01-22  5:14 ` [PATCH teavpn2 0/5] Update README, Refactor and Fix Config Template Ammar Faizi
2022-01-22  5:41   ` Ammar Faizi
2022-01-22  5:44     ` Alviro Iskandar Setiawan [this message]
2022-01-22  5:48       ` 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='CAOG64qPXKs0i=JMAUHwoWFaC+7sC92BxZKq4ghsgvEPszMyHDw@mail.gmail.com' \
    [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