public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: David James <davidjames@google.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] Add a test case for --newuse, --changed-use, and --binpkg-respect-use.
Date: Mon, 24 Feb 2014 11:03:52 -0800	[thread overview]
Message-ID: <CAGNm6ewi3+oqM6OyQs=H-WHM4h0D4QrAv4L5_3FMCMSRTLCa5A@mail.gmail.com> (raw)
In-Reply-To: <20140224105659.37ffe539.dolsen@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

On Mon, Feb 24, 2014 at 10:56 AM, Brian Dolbec <dolsen@gentoo.org> wrote:

> On Mon, 24 Feb 2014 10:14:26 -0800
> David James <davidjames@google.com> wrote:
>
> > Change-Id: I201e468c6e7cda6aa961371ad9ddc10cfab04bc7
> > ---
> >  pym/portage/tests/resolver/test_useflags.py | 78
> +++++++++++++++++++++++++++++
> >  1 file changed, 78 insertions(+)
> >  create mode 100644 pym/portage/tests/resolver/test_useflags.py
> >
> >
>
> Was there a difference in this posting to the one last Thursday?
>
> If not a simple bump reminder was all that should have been done.
>
> If it is different, they you should have created the patch with the
> -v 2  format-patch option.  And summarized the changes.
>
> Sebastian I believe, has had the most experience with the tests, so I
> will leave the review up to him, Mike.


It's the same patch -- I just accidentally sent it twice. So consider this
a bump, then.

[-- Attachment #2: Type: text/html, Size: 1383 bytes --]

  reply	other threads:[~2014-02-24 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 18:14 [gentoo-portage-dev] [PATCH] Add a test case for --newuse, --changed-use, and --binpkg-respect-use David James
2014-02-24 18:56 ` Brian Dolbec
2014-02-24 19:03   ` David James [this message]
2014-02-24 20:07     ` Sebastian Luther
  -- strict thread matches above, loose matches on Subject: below --
2014-02-20 18:43 David James

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='CAGNm6ewi3+oqM6OyQs=H-WHM4h0D4QrAv4L5_3FMCMSRTLCa5A@mail.gmail.com' \
    --to=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