xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "michele.paolino" <michele.paolino@studio.unibo.it>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: generate random numbers
Date: Wed, 3 Mar 2010 08:52:47 +0100	[thread overview]
Message-ID: <14f366f91003022352p60afaa73va9c29f9c0eaeb6cd@mail.gmail.com> (raw)
In-Reply-To: <4B8D0B6D.6030607@eu.citrix.com>

thanks,
I have solved the timer.c problem right now. I am able to start dom0.

Michele

On 3/2/10, George Dunlap <george.dunlap@eu.citrix.com> wrote:
> michele.paolino wrote:
>> I'm really sorry, maybe I misunderstood your mail.  I don't want
>> anyone to work for me.:-)
> Whenever you ask a question, you're asking someone to work for you,
> because it takes time and effort for someone to answer it.  Even a short
> e-mail response may take 5 minutes of reading, understanding, thinking,
> and typing.  To answer your question about the BUG() requires me to
> download the repository you're using, look at and trace around code I've
> never looked at before, and possibly to read and understand your code.
> That's probably at least a half-hour of my time.
>
> And that's OK.  I like helping people, I like solving problems.  It's
> also an investment: if you become a good OS coder, the computer industry
> as a whole (and myself included in that) benefit; and if you become
> better at Xen, I benefit more directly.
>
> However, I don't want to waste my time.  How you can demonstrate to me
> that you are committed to learning this, and that you are capable of
> becoming an OS coder, is by demonstrating that you've spent effort and
> thought on something before answering a question.
>
> I'll take a closer look and try to answer your question either later
> today or tomorrow.
>
>  -George
>

      reply	other threads:[~2010-03-03  7:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 20:31 generate random numbers michele.paolino
2010-02-12  1:51 ` James Harper
2010-02-12  8:32   ` michele.paolino
2010-02-12 12:15     ` George Dunlap
2010-02-12 22:42       ` michele.paolino
2010-02-12 23:12         ` Daniel Stodden
2010-02-25 18:31           ` michele.paolino
2010-02-25 21:25             ` George Dunlap
2010-02-26 17:43               ` michele.paolino
2010-02-26 17:44                 ` George Dunlap
2010-02-26 18:54                   ` michele.paolino
2010-03-01 11:41                     ` George Dunlap
2010-03-01 16:56                       ` michele.paolino
2010-03-02 12:58                         ` George Dunlap
2010-03-03  7:52                           ` michele.paolino [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=14f366f91003022352p60afaa73va9c29f9c0eaeb6cd@mail.gmail.com \
    --to=michele.paolino@studio.unibo.it \
    --cc=Xen-devel@lists.xensource.com \
    --cc=george.dunlap@eu.citrix.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 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).