From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: app-portage/cfg-update
Date: Sun, 02 Oct 2011 10:26:09 +0100 [thread overview]
Message-ID: <4E882E31.3030606@gentoo.org> (raw)
In-Reply-To: <CAGfcS_=e1XVf3G9wrWqE6e-Fxg5yX_DvTY1GZNheKxQ=Pvdzyg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 10/02/2011 03:26 AM, Rich Freeman wrote:
> On Sat, Oct 1, 2011 at 4:36 PM, Markos Chandras
> <hwoarang@gentoo.org> wrote:
>> # Markos Chandras <hwoarang@gentoo.org> (01 Oct 2011) #
>> Unmaintained. Plenty of open bugs ( 219892, 230183, 303199 ). #
>> Replaced by dispatch-conf and/or etc-update # Masked for removal
>> in 30 days. app-portage/cfg-update
>
> If nobody else is interested I think I might take this one - I find
> it handy. I forked a copy to github and merged in the patches
> from portage, and will see about addressing the other two bugs
> (though from what I can tell one seems rare and the other seems
> similar to a known issue in dispatch-conf so they should be
> low-priority).
>
> If there are other issues festering that I should be aware of
> before keeping it around please let me know.
>
> Not being a master of perl or portage hooks I'm not sure how much
> I'll be able to extend it, but I can at least be responsive to bugs
> and patches, and can make the decision to terminate it if it
> becomes unmanageable. If anybody is interested in contributing to
> it (or taking it over if you'll be more active) let me know.
>
> Rich
>
Excellent. Please remove the mask and it is all yours ;)
- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIcBAEBCgAGBQJOiC4xAAoJEPqDWhW0r/LCDRcP/RhuNENUeI9fy+EzTre0gSbb
l29jTRUXsQbmprLUkGA1FojZKn15mfj8FLu7XdLCTz6bYris/e4hiiBWX+sQhOcv
vsJAg8GDvbqyNX8nHeSEtPWOkIDOsd8yoLJeAuq2sdsX9QEnqLlARMRdXpR8lyn0
6iU4IOvhWrpuB7xaEvuWf5C3MNMoSriyIdA3GL/ZjCqiwZO7C1YgNj9n4xB/5fA2
+r371mz3Cnv1CECi9opLf1sHhveWvpJ1W6gy3xIENBQvkhhw2hIc3DWyJ/Xwt3cb
YRDVHV0074EPSroiEZbEIDN7jWeFuDv2nbx/r1U5Xk7vBhQ/siglq89fGc+EEj8H
/lr/TDpiVGEtXW1/O3XbtcEmtlALC+M705SLQyeulTy/KnUP+bP7B20IX3DT7HEm
5v543DafebuIcpJ3/24/F6EjMjHlCw0h2sano5w2sGknu8WUkj90upMgYwx/d3cw
MTEE8Srk0A3P3UYOG+lpvhvvYxdGg4qAM9j6E2pRztirG4RAq29+95AN+pL2LE6U
NxVyfYGYsCP22otyVf5DPBi3hEdHsdqf5HXQX3Z4yVK3h18zWf1PIgluEw6yijU9
IIblr4OW+Lq3PTkin1bA2d+hOoxoTlG+AVljKlz3x/8gRGSE+7sDzsM0IOtISs8c
l9xfB98pzFEGzu6bO/by
=2OqI
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-10-02 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 20:36 [gentoo-dev] Last rites: app-portage/cfg-update Markos Chandras
2011-10-02 2:26 ` Rich Freeman
2011-10-02 9:26 ` Markos Chandras [this message]
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=4E882E31.3030606@gentoo.org \
--to=hwoarang@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