From: Laszlo Ersek <lersek@redhat.com>
To: Rob Landley <rob@landley.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] multiple -append?
Date: Sat, 13 May 2017 00:48:56 +0200 [thread overview]
Message-ID: <d15aabb2-2313-4b2e-4e88-0649664aaf01@redhat.com> (raw)
In-Reply-To: <dcc8c16f-7d4d-3fdf-a1e8-508548239bb1@landley.net>
On 05/12/17 16:20, Rob Landley wrote:
> When I feed a second -append to qemu-system-i386 they don't get
> concatenated, the second replaces the first. Why is it called "append" then?
This behavior dates back to commit a20dd508aa38 ("simplified invocation
- added automatic IDE disk geometry guessing to reuse old disk images
directly", 2003-09-30), which is when "-append" was added.
In said commit, "kernel_cmdline" was *appended* to "params->commandline"
with pstrcat(). The rest is history.
TL;DR: "just because" :)
Thanks
Laszlo
prev parent reply other threads:[~2017-05-12 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 14:20 [Qemu-devel] multiple -append? Rob Landley
2017-05-12 22:48 ` Laszlo Ersek [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=d15aabb2-2313-4b2e-4e88-0649664aaf01@redhat.com \
--to=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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).