From: "Raphaël Enrici" <blacknoz@club-internet.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] openbsd image on freeoszoo
Date: Sat, 10 Jul 2004 09:50:30 +0200 [thread overview]
Message-ID: <40EF9FC6.3000507@club-internet.fr> (raw)
In-Reply-To: <20040709231808.GA17856@jbrown.mylinuxbox.org>
Jim C. Brown wrote:
>My apologies but I don't have the email address of the FreeOSZoo
>maintainer. I merely want to make some comments that might help make
>improvements.
>
>
Hi Jim,
thanks for your report, I have no openbsd skill [that's one of the
images I want to try asap] so I won't be able to help for now. Contacts
are listed in the community page.
@Jean-Michel, this report makes me think to one of our last thread
concerning freeoszoo security concern, that may be helpful to have a
"maintainer" notion so that people stay "responsibles" (I mean they at
least want to take care of evolutions and or bug reported by users &
developers) of uploads they do ? It does not mean in any case that
anybody should not help anymore, it's just a kind of trace of what was
done by who and how.
What do you (all of you) think about it ?
Have a nice day and have fun!
Raphaël
http://freeoszoo.org/~blacknoz
next prev parent reply other threads:[~2004-07-10 7:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 23:18 [Qemu-devel] openbsd image on freeoszoo Jim C. Brown
2004-07-10 1:27 ` [Qemu-devel] " Jim C. Brown
2004-07-10 12:00 ` Julian Seward
2004-07-10 15:16 ` Jim C. Brown
2004-07-10 14:45 ` Fabrice Bellard
2004-07-10 20:52 ` Jim C. Brown
2004-07-10 21:46 ` [Qemu-devel] cvs cpu-exec.c (bug?) Renzo Davoli
2004-07-10 22:23 ` [Qemu-devel] Re: openbsd image on freeoszoo Julian Seward
2004-07-11 0:52 ` Jim C. Brown
2004-07-12 12:12 ` Julian Seward
2004-07-10 7:50 ` Raphaël Enrici [this message]
2004-07-11 0:16 ` [Qemu-devel] " Stefano Marinelli
2004-07-11 0:53 ` Jim C. Brown
2004-07-11 7:22 ` Stefano Marinelli
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=40EF9FC6.3000507@club-internet.fr \
--to=blacknoz@club-internet.fr \
--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 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.