From: Fabrice Bellard <fabrice@bellard.org>
To: Hetz Ben Hamo <hetzbh@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU Forum news
Date: Wed, 22 Dec 2004 23:57:45 +0100 [thread overview]
Message-ID: <41C9FBE9.9080406@bellard.org> (raw)
In-Reply-To: <41e41e7a041221184828f25318@mail.gmail.com>
Hetz Ben Hamo wrote:
> Hi People,
>
> I found a bit of time tonight to do some upgrades to my hosted virtual machine..
>
> I updated the phpBB forum to 2.0.11 with the security fixes, and
> decided to add the option to add attachments..
>
> You can now add patches, screenshots, logs, whatever you think will
> interest the QEMU community to the "Patches Repository". I limited the
> attachment upload to 50K and limited the file acceptance to source
> code, patches, and graphical format (not including flash, video etc)..
>
> If you're posting a patch, please follow the following steps:
>
> 1. Make sure you have a unified patch (you can create one with the
> command: diff -u orig-file modified-file > diff.patch). If it's big,
> gzip (or bzip) it (that way many browsers won't open it directly into
> the browser window).
> 2. Try to make the patch work with the latest version of QEMU (either
> my snapshots or CVS, or the latest official release).
> 3. Add some instructions how to apply, any new command line syntax and
> explanations..
> 4. Add your email address to your post so people can contact you..
> 5. If your posted patches were committed to the CVS, please add a note
> to the post (or email me and I'll do it for you).
>
> Comments are always welcome ;)
Note: you should also send the patches to the qemu-devel mailing list so
that I can more easily look at them...
Fabrice.
prev parent reply other threads:[~2004-12-22 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 2:48 [Qemu-devel] QEMU Forum news Hetz Ben Hamo
2004-12-22 22:57 ` Fabrice Bellard [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=41C9FBE9.9080406@bellard.org \
--to=fabrice@bellard.org \
--cc=hetzbh@gmail.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).