From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: David James <davidjames@google.com>
Subject: Re: [gentoo-portage-dev] [PATCH] Implement --newrepo flag.
Date: Mon, 17 Feb 2014 02:45:19 -0500 [thread overview]
Message-ID: <1838050.g4asPsapTS@vapier> (raw)
In-Reply-To: <CAGNm6eyH5hE73ad7vshwSw_J0TXDHwka92OTfPB91Lo4uTFfXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On Friday, February 14, 2014 09:31:19 David James wrote:
> The --newrepo flag tells emerge to recompile a package if it is now being
> pulled from a different repository.
>
> BUG=chromium:200417
> TEST=Verify ebuilds get pulled in when repo changes.
> ---
> man/emerge.1 | 5 +++
> pym/_emerge/create_depgraph_params.py | 1 +
> pym/_emerge/depgraph.py | 80
> ++++++++++++++++++-----------------
> pym/_emerge/help.py | 2 +-
> 4 files changed, 48 insertions(+), 40 deletions(-)
looks like your client line wrapped everything which is why it's unusable. i
guess you need to use `git send-email` or tell your client to disable line
wrapping when sending out patches. unless gmail is your client in which case
you have to use `git` ;).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-02-17 7:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 17:31 [gentoo-portage-dev] [PATCH] Implement --newrepo flag David James
2014-02-14 20:31 ` Sebastian Luther
2014-02-14 20:43 ` David James
2014-02-14 21:37 ` Sebastian Luther
2014-02-17 4:57 ` David James
2014-02-17 7:49 ` Mike Frysinger
2014-02-17 16:39 ` Brian Dolbec
2014-02-17 17:52 ` David James
2014-02-17 20:09 ` Sebastian Luther
2014-02-17 21:44 ` David James
2014-02-18 17:35 ` Sebastian Luther
2014-02-17 18:23 ` Sebastian Luther
2014-02-17 7:45 ` Mike Frysinger [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=1838050.g4asPsapTS@vapier \
--to=vapier@gentoo.org \
--cc=davidjames@google.com \
--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