From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/glep:glep39 commit in: /
Date: Mon, 10 Apr 2023 17:10:32 +0000 (UTC) [thread overview]
Message-ID: <1681146618.c8410eca3df73098ef489850a781e46cdf097b6e.ulm@gentoo> (raw)
commit: c8410eca3df73098ef489850a781e46cdf097b6e
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 10 13:17:41 2023 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Apr 10 17:10:18 2023 +0000
URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=c8410eca
glep-0039: Fix whitespace
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
glep-0039.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/glep-0039.rst b/glep-0039.rst
index a38dbd4..dfa0149 100644
--- a/glep-0039.rst
+++ b/glep-0039.rst
@@ -86,12 +86,12 @@ Problems with the existing system
1. The assumption that TLPs are complete is either incorrect (there
still is no "server" TLP) or just plain weird (but the lack of a
server TLP is technically okay because all devs who don't have an
- obvious TLP belong to the "base" TLP by default).
+ obvious TLP belong to the "base" TLP by default).
2. There is nothing at all to ensure that project leads actually do
represent the devs they supposedly lead or satisfy their
responsibilities. Indeed, should a TLP manager go AWOL it is not at
all obvious how the situation should be resolved.
-3. Nothing is being decided at global scope right now. Some TLP strategic
+3. Nothing is being decided at global scope right now. Some TLP strategic
managers rarely attend the managers' meetings, and the managers as a
whole certainly are not providing any sort of global vision for
Gentoo right now.
@@ -179,7 +179,7 @@ B. Global issues will be decided by an elected Gentoo council.
Rationale
=========
-So, does this proposal solve any of the previously-mentioned problems?
+So, does this proposal solve any of the previously-mentioned problems?
1. There is no longer any requirement that the project structure be
complete. Some devs work on very specific parts of the tree, while
next reply other threads:[~2023-04-10 17:10 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 17:10 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-08 17:12 [gentoo-commits] data/glep:master commit in: / Ulrich Müller
2023-04-16 8:08 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-05-08 17:12 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-16 8:08 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-05-08 17:12 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-16 8:08 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-05-08 17:12 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-16 8:08 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-05-08 17:12 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-16 8:08 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-05-08 17:12 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-16 8:08 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-05-08 10:35 Ulrich Müller
2023-05-08 10:35 Ulrich Müller
2023-05-02 19:10 Ulrich Müller
2023-04-16 8:08 Ulrich Müller
2023-04-16 8:08 Ulrich Müller
2023-04-16 8:08 Ulrich Müller
2023-04-16 8:08 Ulrich Müller
2023-04-16 8:08 Ulrich Müller
2023-04-10 17:56 Ulrich Müller
2023-04-10 17:10 ` Ulrich Müller
2023-04-10 17:56 Ulrich Müller
2023-04-10 17:52 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 17:10 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-10 13:29 Ulrich Müller
2023-04-01 9:04 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-10 13:29 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-04-01 9:04 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-10 13:29 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-03-12 20:14 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-10 13:29 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-03-12 20:10 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-10 13:29 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
2023-03-12 20:10 [gentoo-commits] data/glep:master " Ulrich Müller
2023-04-10 13:29 ` [gentoo-commits] data/glep:glep39 " Ulrich Müller
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=1681146618.c8410eca3df73098ef489850a781e46cdf097b6e.ulm@gentoo \
--to=ulm@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