From: Alexander Berntsen <bernalex@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH 2/2] runtests: fix output for skipped pythons
Date: Sun, 20 Mar 2016 14:53:01 +0100 [thread overview]
Message-ID: <56EEAB3D.6020303@gentoo.org> (raw)
In-Reply-To: <1458422972-22690-1-git-send-email-slyfox@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Replying to this email segfaulted my Thunderbird... I'll try this again:
Nice! This LGMT too, and I'll commit and push it Monday with the other
one unless there are any objections.
However, Sergei, when you're sending related patches, please send them
to the same thread. git send-email should do this by default. Buuuut
these patches *aren't* related, so there shouldn't be a counter there
in the first place. ;)
Thanks for the patches!
- --
Alexander
bernalex@gentoo.org
https://secure.plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJW7qs9AAoJENQqWdRUGk8BDoMQAIhrlsY14r/B8Otbhgzbhh9T
Jol7FqInCZ/BPKmBJPhlSQiFB9SESSavxUYAVGYS/8xOjWnwU4aiiwHfmszrOD+Y
9ZgMly6mqefNsxSfBiurd8BuSFMm8l9bSkXmZyPTwAi2qsGt+j0QFlQg/6A4uLQ9
bem9tZzxvxmSLADhmdT9h2ONV9sjJq3gzzJ9+Ri5hcDByiwBXcqWNvh/IuayVE5y
cC5CwnwZ/axuiOJQJwLMKCgTC3kLlZm+8x7D1mBS8J0RErVFj8ieoJtqHsLlR35d
RuW1dwWfTiXkL/Mh0j6VVqXnqlTGRMMWexk7C4JQo2ecN065jv6xs3ZBtmhdPKAQ
cP5QMEyjr2talIMRxkPGp1msFuQu5CnR540iC5Ic0ePk9KJt0RNmna9+Zc/r//vr
OoFCFmDtvU5Kf43EW/DlHy4yLpe8wyh7UHEm2h+sVedf/jh6gEb8XUVsSohiUveJ
u4X8xhMzQnuOa1FIuuLbxecYUxReEcAJgdD/2ahYnQDPrwo+1GOH+zjSCv9UeNW2
dVCV5d774YcRJ1sVtqBugx4OV7dveTXbknBjp/cXkTq04Na7HWjpIve+8tA37B04
aqRlnlXi8G1OM8sLUjYRt9ogQ/eR6hldEq50iW8ROW8QSU58h6Qjk5JCEVuXb0m6
5ahuJEGflOU9fCrpgVdX
=s0Zw
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-03-20 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 21:29 [gentoo-portage-dev] [PATCH 2/2] runtests: fix output for skipped pythons Sergei Trofimovich
2016-03-20 13:53 ` Alexander Berntsen [this message]
2016-03-24 22:33 ` Sergei Trofimovich
2016-03-29 10:12 ` Alexander Berntsen
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=56EEAB3D.6020303@gentoo.org \
--to=bernalex@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