From: Anton Ivanov <anton.ivanov@cambridgegreys.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-um@lists.infradead.org
Subject: Re: UML HowTo rewrite
Date: Wed, 22 Apr 2020 14:30:23 +0100 [thread overview]
Message-ID: <cbf1b59a-e6d5-5870-76dc-60455fb179fa@cambridgegreys.com> (raw)
In-Reply-To: <1a7a4aa7-aa01-9747-202a-b93ffb5c657a@cambridgegreys.com>
On 20/04/2020 09:33, Anton Ivanov wrote:
>
>
> On 20/04/2020 09:30, Johannes Berg wrote:
>> Hi Anton,
>>
>>> Can we have a couple of sections on how to use time travel, virtio,
>>> etc so I can add the to the new howtos?
>>
>> Yeah, I guess that makes sense, at least for the parts that are actually
>> done :)
>>
>> Want to merge it, and I'll add something as patches later? Seems easier
>> (especially for new content)?
>
> Sure. I hope to finish cleaning up the base content today and we can handle
> everything as PRs/Patches from there onward.
The initial content is more or less in place.
Comments and PRs to change/add things are welcome.
https://github.com/kot-begemot-uk/uml-howto-v2
>
>>
>> johannes
>>
>>
>> _______________________________________________
>> linux-um mailing list
>> linux-um@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-um
>>
>
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2020-04-22 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 8:01 UML HowTo rewrite Anton Ivanov
2020-04-20 8:30 ` Johannes Berg
2020-04-20 8:33 ` Anton Ivanov
2020-04-22 13:30 ` Anton Ivanov [this message]
2020-04-22 13:47 ` Johannes Berg
2020-04-22 13:53 ` Anton Ivanov
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=cbf1b59a-e6d5-5870-76dc-60455fb179fa@cambridgegreys.com \
--to=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.