From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Uncoordinated changes
Date: Tue, 16 Feb 2016 20:51:39 -0500 [thread overview]
Message-ID: <CAGfcS_=vh3GX4OwtN4rwy2g5kDgFdi4R9_yp4JqPEN4ZvBYDQg@mail.gmail.com> (raw)
In-Reply-To: <20160216165545.4ad457cf@tundra.gateway.pace.com>
On Tue, Feb 16, 2016 at 5:55 PM, Ryan Hill <rhill@gentoo.org> wrote:
> On Sun, 14 Feb 2016 10:58:10 -0500
> Rich Freeman <rich0@gentoo.org> wrote:
>
>> Well, if debugging is your only concern, on the system you're going to
>> debug from:
>> touch herds.xml
>
> Don't do that.
>
> rhill@tundra /usr/portage/dev-util/creduce $ repoman
>
> RepoMan scours the neighborhood...
> [INFO] checking package dev-util/creduce
> Traceback (most recent call last):
See, you're uncovering bugs already. :)
I wasn't really serious. The suggestion was to stick an empty
herds.xml in the tree, and my point was that anybody can basically do
that already.
--
Rich
next prev parent reply other threads:[~2016-02-17 1:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 20:15 [gentoo-dev] Uncoordinated changes Patrick Lauer
2016-02-12 1:34 ` Rich Freeman
2016-02-12 19:11 ` Paul Varner
2016-02-12 7:48 ` Michał Górny
2016-02-12 9:07 ` Patrick Lauer
2016-02-12 11:16 ` Rich Freeman
2016-02-12 22:02 ` Michał Górny
2016-02-13 21:47 ` Raymond Jennings
2016-02-13 22:44 ` Rich Freeman
2016-02-14 0:58 ` Raymond Jennings
2016-02-14 1:16 ` Rich Freeman
2016-02-14 3:55 ` Raymond Jennings
2016-02-14 10:33 ` [gentoo-dev] herds.xml removal (was: Re: Uncoordinated changes) Ulrich Mueller
2016-02-14 15:30 ` [gentoo-dev] Uncoordinated changes Patrick Lauer
2016-02-14 15:58 ` Rich Freeman
2016-02-16 22:55 ` [gentoo-dev] " Ryan Hill
2016-02-17 1:51 ` Rich Freeman [this message]
2016-02-14 18:30 ` [gentoo-dev] " Patrick Lauer
2016-02-14 11:37 ` Patrick Lauer
2016-02-14 12:18 ` Rich Freeman
2016-02-14 18:44 ` Andreas K. Hüttel
2016-02-14 18:53 ` Patrick Lauer
2016-02-14 18:59 ` Ciaran McCreesh
2016-02-15 3:24 ` Daniel Campbell
2016-02-14 13:15 ` Kent Fredric
2016-02-14 14:37 ` Michał Górny
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='CAGfcS_=vh3GX4OwtN4rwy2g5kDgFdi4R9_yp4JqPEN4ZvBYDQg@mail.gmail.com' \
--to=rich0@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