From: Tom Wijsman <TomWij@gentoo.org>
To: creffett@gentoo.org
Cc: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH v4] Add repoman check to warn if src_prepare/src_configure are used in EAPI 0/1 and if pkg_pretend is used in EAPI < 4. Fixes bug 379491.
Date: Wed, 15 Jan 2014 23:54:45 +0100 [thread overview]
Message-ID: <20140115235445.5d92655d@TOMWIJ-GENTOO> (raw)
In-Reply-To: <1389821748-18454-1-git-send-email-creffett@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
On Wed, 15 Jan 2014 16:35:48 -0500
Chris Reffett <creffett@gentoo.org> wrote:
> ---
> pym/repoman/checks.py | 31 ++++++++++++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
Can you please use In-Reply-To to avoid threads from breaking?
Due to the patches being in four threads, collapsing the threads gives
me four threads instead of a single thread. If everyone does this, it
becomes tedious to follow what is going on. This also doesn't allow one
to ignore threads which one cannot help on or has no interest in.
Thank you very much in advance.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2014-01-15 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 21:35 [gentoo-portage-dev] [PATCH v4] Add repoman check to warn if src_prepare/src_configure are used in EAPI 0/1 and if pkg_pretend is used in EAPI < 4. Fixes bug 379491 Chris Reffett
2014-01-15 22:23 ` [gentoo-portage-dev] " Duncan
2014-01-15 22:54 ` Tom Wijsman [this message]
2014-01-19 9:22 ` [gentoo-portage-dev] " Mike Frysinger
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=20140115235445.5d92655d@TOMWIJ-GENTOO \
--to=tomwij@gentoo.org \
--cc=creffett@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