From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: <xen-devel@lists.xenproject.org>, Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH v1] automation: document how to refresh a container
Date: Fri, 9 Jul 2021 13:28:25 +0100 [thread overview]
Message-ID: <befa4ec9-33c1-6bc8-c2c4-f0187d3012a9@citrix.com> (raw)
In-Reply-To: <20210709142333.45b5795b.olaf@aepfle.de>
On 09/07/2021 13:23, Olaf Hering wrote:
> Am Fri, 9 Jul 2021 13:02:54 +0100
> schrieb Andrew Cooper <andrew.cooper3@citrix.com>:
>
>> Do we need the ls here? That sounds a little like debugging.
> Maybe not, it may show a long list of unrelated stuff.
> It is just to verify a fresh container exists, as you said, just for debugging.
Ok - I'll drop that line and commit, then we can see about rebuilding
the container.
~Andrew
prev parent reply other threads:[~2021-07-09 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 14:56 [PATCH v1] automation: document how to refresh a container Olaf Hering
2021-07-09 12:02 ` Andrew Cooper
2021-07-09 12:23 ` Olaf Hering
2021-07-09 12:28 ` Andrew Cooper [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=befa4ec9-33c1-6bc8-c2c4-f0187d3012a9@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).