From: "Paul Varner" <fuzzyray@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoolkit:master commit in: /
Date: Tue, 24 Nov 2015 18:12:35 +0000 (UTC) [thread overview]
Message-ID: <1448388601.1415ee6c58c52633b801bac79810f9cf463987d7.fuzzyray@gentoo> (raw)
commit: 1415ee6c58c52633b801bac79810f9cf463987d7
Author: Paul Varner <fuzzyray <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 24 18:10:01 2015 +0000
Commit: Paul Varner <fuzzyray <AT> gentoo <DOT> org>
CommitDate: Tue Nov 24 18:10:01 2015 +0000
URL: https://gitweb.gentoo.org/proj/gentoolkit.git/commit/?id=1415ee6c
Update documentation
Add a pointer to gitweb in Changelog
Update policy for creating releases in README.dev
Remove obsolete TODO file
ChangeLog | 3 +++
README.dev | 11 ++++++++---
TODO | 33 ---------------------------------
3 files changed, 11 insertions(+), 36 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 7524886..a7ff478 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,6 @@
+Please see https://gitweb.gentoo.org/proj/gentoolkit.git/log/
+Alternatively, you can use 'git log' on a copy of the repository
+
2010-01-04: Paul Varner <fuzzyray@gentoo.org>
* euse: Merge euse from bug #259318 written by Jared Hancock. This
version is a significant rewrite and add supports for utilizing
diff --git a/README.dev b/README.dev
index 62a35fe..e7f81e6 100644
--- a/README.dev
+++ b/README.dev
@@ -7,11 +7,16 @@ We only have several requirements. If you want to do a major change (i.e
rewrite/refactor something), please talk to us before pushing any
commits. If you break something, please fix it.
-If you want a new release of gentoolkit or gentoolkit-dev, please coordinate
-it with fuzzyray (gentoolkit) or idl0r (gentoolkit-dev).
+All members of the Portage or Portage Tools projects are authorized to
+create a new release of gentoolkit or gentoolkit-dev.
+
+All other Gentoo Developers are authorized to create a new release if it is
+coordinated with fuzzyray and/or dolsen.
+
+If you create a release and it breaks, please fix it.
Any non Gentoo developers who wish to contribute, the best way to get
-started is by pulling a copy of the repository and submitting patches to
+started is by clonig a copy of the repository and submitting patches to
bugzilla. Additionally, we can be found in the #gentoo-portage IRC
channel.
diff --git a/TODO b/TODO
deleted file mode 100644
index 1cee1a4..0000000
--- a/TODO
+++ /dev/null
@@ -1,33 +0,0 @@
-- equery:
- - add --overlay, --portdir to uses
- - add glsa pkgspec
- - query for current GLSAs on installed package(s)
-- rewrite ekeywords and echangelog to use gentoolkit
-- merge change and echangelog
-- merge useflag and euse, have _one_ command line tool
- - update ufed to rely on the CLI tool
- - update ufed to rely on generate-use
- - merge generate-use and ufed?
-- write efeatures for turning on/off FEATURES in make.conf
-- look at ekeys, ewatch
-- revision bump tool
- - bump versioned files in filesdir
- - -m for changelog entry
- - use ~/.gentoo/gentoolkit/ebump.conf
- - use /etc/gentoolkit/ebump.conf
-
-equery (modern):
- Add more --debug stuff
- Write tests for Dependencies._parser
- Profile Dependencies._parser
- Extend PackageFormatter usage to everything that outputs packages to
- allow for purvasive use of -F, --format goodness
-
-Ebuild changes:
- - Add:
- src_test() {
- "${python}" setup.py test || die "testing returned non zero"
- }
-
-For Next Release:
- - write NEWS file
next reply other threads:[~2015-11-24 18:12 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 18:12 Paul Varner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-10 2:28 [gentoo-commits] proj/gentoolkit:master commit in: / Matt Turner
2024-05-08 21:43 Sam James
2024-04-25 20:37 Sam James
2024-03-12 21:43 Sam James
2024-03-12 21:43 Sam James
2024-03-12 21:43 Sam James
2024-02-16 20:39 Sam James
2024-01-19 6:37 Sam James
2024-01-19 4:54 Sam James
2024-01-18 20:57 Matt Turner
2024-01-18 20:57 Matt Turner
2023-12-03 7:51 Sam James
2023-03-24 2:50 Sam James
2023-03-20 4:41 Sam James
2022-07-10 20:49 Brian Dolbec
2022-07-10 18:59 Brian Dolbec
2022-07-10 18:41 Brian Dolbec
2022-07-10 17:20 Brian Dolbec
2022-03-16 18:19 Matt Turner
2022-03-16 18:19 Matt Turner
2022-02-09 10:48 Sam James
2021-09-21 21:01 Matt Turner
2021-09-20 23:02 Matt Turner
2021-09-20 22:57 Matt Turner
2021-09-20 22:57 Matt Turner
2021-09-20 22:57 Matt Turner
2021-03-02 3:31 Matt Turner
2020-04-24 8:34 Michał Górny
2020-04-24 8:06 Michał Górny
2020-03-12 16:51 Matt Turner
2020-02-19 5:44 Michał Górny
2020-01-26 15:20 Michał Górny
2019-08-19 3:51 Zac Medico
2019-05-11 23:09 Virgil Dupras
2019-04-01 1:51 Virgil Dupras
2018-08-14 16:01 Virgil Dupras
2017-03-23 1:40 Mike Frysinger
2017-03-22 20:54 Brian Dolbec
2017-03-22 20:13 Brian Dolbec
2017-03-22 12:51 Brian Dolbec
2016-08-01 4:10 Brian Dolbec
2016-08-01 4:10 Brian Dolbec
2016-03-13 15:11 Mike Gilbert
2015-12-20 20:33 Mike Gilbert
2015-11-24 18:14 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2015-10-15 16:44 Paul Varner
2014-11-03 22:59 Mike Gilbert
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=1448388601.1415ee6c58c52633b801bac79810f9cf463987d7.fuzzyray@gentoo \
--to=fuzzyray@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