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]>,
	Alviro Iskandar Setiawan <[email protected]>
Subject: [PATCH teavpn2 1/5] README: Remove RELEASE_MODE var
Date: Sat, 22 Jan 2022 05:06:29 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Since we use the configure script, we always do -O2 for all builds
and RELEASE_MODE variable is no longer used. Remove it from the
build instruction in README file.

Signed-off-by: Alviro Iskandar Setiawan <[email protected]>
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 8f15aed..c0a650f 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,7 @@ welcomed).
 git clone https://github.com/TeaInside/teavpn2;
 cd teavpn2;
-make -j$(nproc) RELEASE_MODE=1;
+make -j$(nproc);
 # Issues

  reply	other threads:[~2022-01-22  5:06 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 ` Alviro Iskandar Setiawan [this message]
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
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:

* 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] \


* 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