public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: "Martin Liška" <mliska@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add pytest for a GCOV test-case
Date: Thu, 14 Jan 2021 14:27:11 +0100	[thread overview]
Message-ID: <yddczy78x8w.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <yddh7nj8xgu.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Thu, 14 Jan 2021 14:22:25 +0100")

Hi Martin,

>>> * If we now have an (even optional) dependency on python/pytest, this
>>>    (with the exact versions and use) needs to be documented in
>>>    install.texi.
>>
>> Done that.
>
> +be installed. Some optional tests also require Python3 and pytest module.
>
> It would be better to be more specific here.  Or would Python 3.0 and
> pytest 2.0.0 do ;-)

and a nit I just noticed: two spaces after full stop.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2021-01-14 13:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 11:39 Martin Liška
2020-12-22 17:49 ` David Malcolm
2020-12-23 13:03   ` Martin Liška
2021-01-05 23:36     ` Jeff Law
2021-01-07 16:14       ` Martin Liška
2021-01-08 20:29         ` Jeff Law
2021-01-13 13:38         ` Rainer Orth
2021-01-13 14:08           ` David Malcolm
2021-01-13 14:30             ` Rainer Orth
2021-01-14  8:56           ` Martin Liška
2021-01-14 13:22             ` Rainer Orth
2021-01-14 13:27               ` Rainer Orth [this message]
2021-01-14 13:33               ` Martin Liška
2021-01-15 12:28                 ` Rainer Orth
2021-01-15 13:48                   ` Martin Liška

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=yddczy78x8w.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).