public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-libs/axtls/
Date: Mon, 21 Dec 2020 12:08:43 +0000 (UTC)	[thread overview]
Message-ID: <1608552513.acf4d96d58ff7184e641a151385633789ee15aa5.marecki@gentoo> (raw)

commit:     acf4d96d58ff7184e641a151385633789ee15aa5
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 21 12:06:34 2020 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Mon Dec 21 12:08:33 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=acf4d96d

net-libs/axtls-2.1.5-r100: fix accidental whitespace mangling

Thanks to Arfrever for having spotted and reported it.

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 net-libs/axtls/axtls-2.1.5-r100.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/net-libs/axtls/axtls-2.1.5-r100.ebuild b/net-libs/axtls/axtls-2.1.5-r100.ebuild
index a988deef75d..aa38483db9f 100644
--- a/net-libs/axtls/axtls-2.1.5-r100.ebuild
+++ b/net-libs/axtls/axtls-2.1.5-r100.ebuild
@@ -105,7 +105,8 @@ use_flag_config() {
 			sed -i -e 's:^CONFIG_HTTP_STATIC_BUILD:# CONFIG_HTTP_STATIC_BUILD:' \
 				config/.config || die
 		fi
-		if ! use cgi-php && ! use cgi-lua; then			sed -i -e 's:^CONFIG_HTTP_HAS_CGI:# CONFIG_HTTP_HAS_CGI:' \
+		if ! use cgi-php && ! use cgi-lua; then
+			sed -i -e 's:^CONFIG_HTTP_HAS_CGI:# CONFIG_HTTP_HAS_CGI:' \
 				config/.config || die
 		fi
 		if ! use cgi-php; then


             reply	other threads:[~2020-12-21 12:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 12:08 Marek Szuba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-09  7:59 [gentoo-commits] repo/gentoo:master commit in: net-libs/axtls/ David Seifert
2021-07-20 19:03 Conrad Kostecki
2021-07-20 19:03 Conrad Kostecki
2021-03-25 23:52 Conrad Kostecki
2021-01-24  3:52 Sam James
2021-01-23 22:51 Sam James
2021-01-23  4:20 Sam James
2021-01-23  4:09 Sam James
2020-06-14 11:21 Sergei Trofimovich
2020-04-24  0:53 Anthony G. Basile
2020-04-20  9:50 Agostino Sarubbo
2020-04-20  9:48 Agostino Sarubbo
2020-04-19 12:16 Agostino Sarubbo
2020-04-19 12:14 Agostino Sarubbo
2020-04-18  9:18 Agostino Sarubbo
2019-03-15 20:41 Anthony G. Basile
2019-03-15 20:41 Anthony G. Basile
2018-07-21 19:47 Mikle Kolyada
2018-01-04 16:52 Mikle Kolyada
2017-10-26 18:54 Thomas Deutschmann
2017-09-24 16:16 Sergei Trofimovich
2017-09-24 10:46 Sergei Trofimovich
2017-09-23 13:55 Sergei Trofimovich
2017-09-23 12:35 Sergei Trofimovich
2017-09-22  5:50 Markus Meier
2017-09-12  1:20 Anthony G. Basile
2017-06-26  7:54 Alexis Ballier
2017-02-22 14:36 Anthony G. Basile
2016-12-31 18:37 Anthony G. Basile
2016-12-22  0:41 Anthony G. Basile
2016-12-22  0:41 Anthony G. Basile
2016-08-31 21:59 Anthony G. Basile
2016-08-17 18:23 Anthony G. Basile
2016-07-07  0:03 Anthony G. Basile
2016-07-07  0:03 Anthony G. Basile
2015-11-26 19:27 Markus Meier
2015-11-12  9:40 Agostino Sarubbo
2015-11-11  9:12 Agostino Sarubbo
2015-11-09 10:31 Agostino Sarubbo
2015-11-08  6:25 Jeroen Roovers

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=1608552513.acf4d96d58ff7184e641a151385633789ee15aa5.marecki@gentoo \
    --to=marecki@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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