From: "Daniel P. Berrangé" <berrange@redhat.com>
To: aidan_leuck@selinc.com
Cc: qemu-devel@nongnu.org, kkostiuk@redhat.com
Subject: Re: [PATCH v2 2/2] Refactor common functions between POSIX and Windows implementation
Date: Fri, 22 Mar 2024 10:15:19 +0000 [thread overview]
Message-ID: <Zf1aN16SJbFqzMJb@redhat.com> (raw)
In-Reply-To: <20240321160725.340341-3-aidan_leuck@selinc.com>
On Thu, Mar 21, 2024 at 04:07:25PM +0000, aidan_leuck@selinc.com wrote:
> From: aidaleuc <aidan_leuck@selinc.com>
>
> Signed-off-by: aidaleuc <aidan_leuck@selinc.com>
> ---
> qga/commands-posix-ssh.c | 47 +--------------------------
> qga/commands-ssh-core.c | 57 ++++++++++++++++++++++++++++++++
> qga/commands-ssh-core.h | 8 +++++
> qga/commands-windows-ssh.c | 66 +-------------------------------------
> qga/meson.build | 3 +-
> 5 files changed, 69 insertions(+), 112 deletions(-)
> create mode 100644 qga/commands-ssh-core.c
> create mode 100644 qga/commands-ssh-core.h
Moving of existing functions into a common file should
be the *first* patch in the series, rather than copying
functions into the windows impl only to immediately
remove them again.
> diff --git a/qga/commands-ssh-core.c b/qga/commands-ssh-core.c
> new file mode 100644
> index 0000000000..51353b396d
> --- /dev/null
> +++ b/qga/commands-ssh-core.c
> \ No newline at end of file
Again, please ensure all files retain a final newline in the file.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2024-03-22 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:07 [PATCH v2 0/2] Implement SSH commands in QEMU GA for Windows aidan_leuck
2024-03-21 16:07 ` [PATCH v2 1/2] " aidan_leuck
2024-03-22 10:31 ` Daniel P. Berrangé
2024-03-22 14:24 ` Aidan Leuck
2024-03-21 16:07 ` [PATCH v2 2/2] Refactor common functions between POSIX and Windows implementation aidan_leuck
2024-03-22 10:15 ` Daniel P. Berrangé [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=Zf1aN16SJbFqzMJb@redhat.com \
--to=berrange@redhat.com \
--cc=aidan_leuck@selinc.com \
--cc=kkostiuk@redhat.com \
--cc=qemu-devel@nongnu.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).