public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Wolfgang E. Sanyer" <wolfgangesanyer@gmail.com>
Subject: Re: [gentoo-dev] [PATCH] flag-o-matic.eclass: get rid of eutils in <EAPI-8, fix eclassdoc, make some funcs internal
Date: Thu, 01 Apr 2021 15:42:54 +0200	[thread overview]
Message-ID: <2482845.vYhyI6sBWr@tuxbook> (raw)
In-Reply-To: <CACwN4LwBX7zAYMGyMeFUxMVZtmRZUS+nS2qptDA08=OQ8zOa0Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

On Mittwoch, 31. März 2021 12:03:33 CEST Wolfgang E. Sanyer wrote:
> I'm curious - why the split e.g. test-flag-PROG() and _test-flag-PROG()? Is
> this stylistic, or does it serve a functional purpose? (Hah, "functional",
> get it? Because they're functions?!?

We prepend `_` to signify internal API. The existing function name needs to 
stay until <=EAPI-7 support is gone in order not to break potential consumers 
even outside of genoo.git.

Regards

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2021-04-01 13:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31  6:39 [gentoo-dev] [PATCH] flag-o-matic.eclass: get rid of eutils in <EAPI-8, fix eclassdoc, make some funcs internal Andreas Sturmlechner
2021-03-31  7:33 ` Sergei Trofimovich
2021-03-31  7:45   ` Andreas Sturmlechner
2021-03-31  9:13     ` Sergei Trofimovich
2021-03-31 10:03       ` Wolfgang E. Sanyer
2021-04-01 13:42         ` Andreas Sturmlechner [this message]
2021-04-01  9:57   ` [gentoo-dev] [PATCH v2 1/5] " Andreas Sturmlechner
2021-04-01  9:58     ` [gentoo-dev] [PATCH v2 2/5] " Andreas Sturmlechner
2021-04-01  9:59       ` [gentoo-dev] [PATCH v2 3/5] " Andreas Sturmlechner
2021-04-01 10:01         ` [gentoo-dev] [PATCH v2 4/5] " Andreas Sturmlechner
2021-04-01 10:02           ` [gentoo-dev] [PATCH v2 5/5] " Andreas Sturmlechner
2021-04-01 18:40             ` Sergei Trofimovich
2021-04-01 18:39           ` [gentoo-dev] [PATCH v2 4/5] " Sergei Trofimovich
2021-04-01 18:37         ` [gentoo-dev] [PATCH v2 3/5] " Sergei Trofimovich
2021-04-01 21:42         ` Ulrich Mueller
2021-04-02  9:49           ` Andreas Sturmlechner
2021-04-01 18:30       ` [gentoo-dev] [PATCH v2 2/5] " Sergei Trofimovich
2021-04-01 18:26     ` [gentoo-dev] [PATCH v2 1/5] " Sergei Trofimovich
2021-03-31  7:36 ` [gentoo-dev] [PATCH] " Sam James
2021-03-31  9:09 ` Ulrich Mueller
2021-04-01 21:57   ` Sam James

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=2482845.vYhyI6sBWr@tuxbook \
    --to=asturm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=wolfgangesanyer@gmail.com \
    /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