From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org, Brian Dolbec <dolsen@gentoo.org>
Subject: Re: [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references (bug 378603)
Date: Mon, 6 Aug 2018 11:35:32 -0700 [thread overview]
Message-ID: <94a89abe-9c91-7e5f-12a2-10f0566af150@gentoo.org> (raw)
In-Reply-To: <20180806003031.75f4132d@professor-x>
[-- Attachment #1.1: Type: text/plain, Size: 458 bytes --]
On 08/06/2018 12:30 AM, Brian Dolbec wrote:
> All these changes as well as the catlayst changes need to be
> co-ordinated so that snapshots and portage and stages don't precede the
> docs changes.
I suppose all of the docs changes can be made in advance, with mention
of both old a new locations. These commands can be used to check the
local configuration:
portageq get_repo_path / gentoo
portageq distdir
portageq pkgdir
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2018-08-06 18:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 0:23 [gentoo-portage-dev] [PATCH 0/2] Change /usr/portage council approved locations (bug 378603) Zac Medico
2018-08-06 0:23 ` [gentoo-portage-dev] [PATCH 1/2] " Zac Medico
2018-08-06 0:23 ` [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references " Zac Medico
2018-08-06 4:59 ` Ulrich Mueller
2018-08-06 5:46 ` Zac Medico
2018-08-06 6:03 ` Zac Medico
2018-08-06 7:30 ` Brian Dolbec
2018-08-06 10:29 ` Ulrich Mueller
2018-08-06 18:35 ` Zac Medico [this message]
2018-08-06 21:50 ` M. J. Everitt
2018-08-06 22:39 ` Zac Medico
2018-08-06 5:32 ` [gentoo-portage-dev] [PATCH 2/2 v2] " Zac Medico
2018-08-06 7:44 ` Brian Dolbec
2018-08-06 18:46 ` Zac Medico
2019-04-18 17:03 ` [gentoo-portage-dev] [PATCH 2/2 v3] " Zac Medico
2019-04-18 17:28 ` Ulrich Mueller
2019-04-18 17:54 ` Zac Medico
2019-04-18 17:58 ` [gentoo-portage-dev] [PATCH 2/2 v4] " Zac Medico
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=94a89abe-9c91-7e5f-12a2-10f0566af150@gentoo.org \
--to=zmedico@gentoo.org \
--cc=dolsen@gentoo.org \
--cc=gentoo-portage-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