From: Kashyap Chamarthy <kchamart@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Subject: Other pages for docs/devel/ [Was: Re: ... Update URLs of "SubmitAPatch" ...]
Date: Fri, 19 Nov 2021 11:15:20 +0100 [thread overview]
Message-ID: <YZd5OLlyKegEphY9@paraplu> (raw)
In-Reply-To: <99a6b686-c2c4-dd5e-fe8c-9940311cdaca@redhat.com>
On Fri, Nov 19, 2021 at 10:09:27AM +0100, Paolo Bonzini wrote:
[...]
> Hi, I'm applying instead
> https://lore.kernel.org/r/20211118074702.216951-2-pbonzini%40redhat.com
> (sorry, you couldn't know of the magic redirect since that's done directly
> on shell.qemu.org's Apache configuration).
Ah, no problem; I missed this one. I sent mine as Thomas mentioned
updating the website on IRC; so I assumed a patch didn't already exist.
> The report-a-bug and security-process pages of the website are also
> candidates for moving to docs/devel, by the way!
Noted; so these two pages:
- https://www.qemu.org/contribute/security-process/
- https://www.qemu.org/contribute/report-a-bug/
What about these two other pages (which are also linked to from the
"contribute"[1] part of the website)? Do they belong to docs/devel? If
not, should they be part of 'qemu-web', instead of the wiki?
- https://wiki.qemu.org/Contribute/FAQ
- https://wiki.qemu.org/Documentation/GettingStartedDevelopers
[1] https://www.qemu.org/contribute/
[...]
--
/kashyap
next prev parent reply other threads:[~2021-11-19 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 17:00 [qemu-web PATCH] Update URLs of "SubmitAPatch" wiki doc Kashyap Chamarthy
2021-11-19 9:09 ` Paolo Bonzini
2021-11-19 10:15 ` Kashyap Chamarthy [this message]
2021-11-24 19:35 ` Other pages for docs/devel/ [Was: Re: ... Update URLs of "SubmitAPatch" ...] Paolo Bonzini
2021-11-25 9:56 ` Kashyap Chamarthy
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=YZd5OLlyKegEphY9@paraplu \
--to=kchamart@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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.