public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: eclass-writing/
Date: Tue, 13 Dec 2011 20:17:36 +0000 (UTC)	[thread overview]
Message-ID: <8576434dcc4712a5001ae498a7ec1dcb737b6333.betelgeuse@gentoo> (raw)

commit:     8576434dcc4712a5001ae498a7ec1dcb737b6333
Author:     Petteri Räty <betelgeuse <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 13 20:11:28 2011 +0000
Commit:     Petteri Räty <betelgeuse <AT> gentoo <DOT> org>
CommitDate: Tue Dec 13 20:11:28 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=8576434d

Add note about changing eclass API

http://www.gentoo.org/proj/en/council/meeting-logs/20111108-summary.txt

---
 eclass-writing/text.xml |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
index caefd7c..1914448 100644
--- a/eclass-writing/text.xml
+++ b/eclass-writing/text.xml
@@ -62,6 +62,13 @@ lot of trouble.
 </p>
 
 <p>
+When removing a function or changing the API of an eclass, make
+sure that it doesn't break any ebuilds in the tree, and post a
+notice to gentoo-dev at least 30 days in advance, preferably with
+a patch included.
+</p>
+
+<p>
 If there is an existing maintainer for an eclass (this is usually the case), you
 <b>must</b> talk to the maintainer before committing any changes.
 </p>



             reply	other threads:[~2011-12-13 20:17 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 20:17 Petteri Räty [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-31  1:21 [gentoo-commits] proj/devmanual:master commit in: eclass-writing/ Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2019-08-30 15:51 Göktürk Yüksek
2019-08-30 15:51 Göktürk Yüksek
2019-09-20 22:52 Göktürk Yüksek
2020-09-18  7:01 Ulrich Müller
2020-12-29 22:08 Göktürk Yüksek
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-09-04 10:33 Ulrich Müller
2021-09-04 10:33 Ulrich Müller
2021-09-04 10:36 Ulrich Müller
2021-09-04 10:36 Ulrich Müller
2021-09-04 10:38 Ulrich Müller
2021-10-13 13:44 Ulrich Müller
2021-12-09  5:01 Sam James
2022-03-16 14:47 Sam James
2022-03-16 14:47 Sam James
2022-03-18 18:10 Sam James
2022-03-18 18:10 Sam James
2022-03-20 13:48 Ulrich Müller
2022-03-23 14:10 Ulrich Müller
2022-03-26 16:16 Ulrich Müller
2022-04-24 12:52 Ulrich Müller
2022-04-28  8:12 Ulrich Müller
2022-04-30 17:01 Ulrich Müller
2023-05-27 18:49 Ulrich Müller
2023-08-26  5:30 Ulrich Müller
2024-01-19 21:06 Ulrich Müller
2024-04-29  6:31 Ulrich Müller
2024-04-29  6:31 Ulrich Müller
2024-04-29  6:31 Ulrich Müller
2024-04-29  6:31 Ulrich Müller
2025-01-06 21:37 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=8576434dcc4712a5001ae498a7ec1dcb737b6333.betelgeuse@gentoo \
    --to=betelgeuse@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