public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [KIRK PATCH 1/1] README: Document passing environment variables
Date: Mon, 10 Jun 2024 14:33:46 +0200	[thread overview]
Message-ID: <a5ef2eef-9061-4591-9613-b2b64cee39dd@suse.com> (raw)
In-Reply-To: <20240610105759.GA710648@pevik>

On 6/10/24 12:57, Petr Vorel wrote:
>> On 6/10/24 11:32, Petr Vorel wrote:
>>> Hi Andrea,
>>>> Hi!
>>>> LGTM
>>>> Reviewed-by: Andrea Cervesato <andrea.cervesato@suse.com>
>>> Thanks, merged as
>>> https://github.com/linux-test-project/kirk/commit/5e8c8064a0b2cee465f2a1dca1cfebef5ade36a2
>>> BTW I wonder if recent kirk commits (SSH fixes) are strong enough to release
>>> kirk and update LTP. WDYT? Or do you wait for ltx improvements before releasing
>>> new version?
>>> Kind regards,
>>> Petr
>> There were really minor updates in kirk. We can probably create a new
>> version after more features will be added, but I have no idea when.
> OK, thanks for info. From the description they looks as a real bug fixes which
> would users appreciated.
>
> Kind regards,
> Petr
>
>> Andrea

Yeah, now that I'm taking a closer look I think you are right. Let's 
make a new kirk version then.

Thank,
Andrea


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2024-06-10 12:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 11:53 [LTP] [KIRK PATCH 1/1] README: Document passing environment variables Petr Vorel
2024-06-10  6:58 ` Andrea Cervesato via ltp
2024-06-10  9:32   ` Petr Vorel
2024-06-10 10:52     ` Andrea Cervesato via ltp
2024-06-10 10:57       ` Petr Vorel
2024-06-10 12:33         ` Andrea Cervesato via ltp [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=a5ef2eef-9061-4591-9613-b2b64cee39dd@suse.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.com \
    --cc=pvorel@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