public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alessandro Barbieri" <lssndrbarbieri@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: profiles/desc/
Date: Fri, 27 May 2022 18:51:34 +0000 (UTC)	[thread overview]
Message-ID: <1653662147.1a0604a2ae590b7dad2d18fa6d313d38caa996e6.Alessandro-Barbieri@gentoo> (raw)

commit:     1a0604a2ae590b7dad2d18fa6d313d38caa996e6
Author:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Fri May 27 14:35:47 2022 +0000
Commit:     Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
CommitDate: Fri May 27 14:35:47 2022 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=1a0604a2

profiles/desc: fix use flags names

Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>

 profiles/desc/parsec_debug.desc | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/profiles/desc/parsec_debug.desc b/profiles/desc/parsec_debug.desc
index 0eb75dccd..6be56f41c 100644
--- a/profiles/desc/parsec_debug.desc
+++ b/profiles/desc/parsec_debug.desc
@@ -3,9 +3,9 @@
 
 # This file contains descriptions of PARSEC_DEBUG USE_EXPAND flags.
 
-debug-history - Keep a summarized history of critical events in memory that can be dumped in gdb when deadlock occur
-debug-mem-addr - Enable the memory access checker
-debug-mem-leak - Enable only the memory leak checker
-debug-mem-race - Enable the memory thread-race checker
-debug-noisier - Enable chatterbox-like verbose debugging (may impact performance)
-debug-paranoid - Enable extra paranoid checks (may impact performance)
+history - Keep a summarized history of critical events in memory that can be dumped in gdb when deadlock occur
+mem-addr - Enable the memory access checker
+mem-leak - Enable only the memory leak checker
+mem-race - Enable the memory thread-race checker
+noisier - Enable chatterbox-like verbose debugging (may impact performance)
+paranoid - Enable extra paranoid checks (may impact performance)


             reply	other threads:[~2022-05-27 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 18:51 Alessandro Barbieri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-03 12:24 [gentoo-commits] repo/proj/guru:master commit in: profiles/desc/ Andrew Ammerlaan
2022-07-03 12:24 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2022-06-15 22:35 Alessandro Barbieri
2022-06-02  1:23 Alessandro Barbieri
2022-05-27 11:28 Alessandro Barbieri
2020-04-28 21:04 Alessandro Barbieri

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=1653662147.1a0604a2ae590b7dad2d18fa6d313d38caa996e6.Alessandro-Barbieri@gentoo \
    --to=lssndrbarbieri@gmail.com \
    --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