All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Bonifazi <stefboombastic@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] qemu-user: relocating target code weakness
Date: Tue, 25 Jan 2011 09:25:20 +0100	[thread overview]
Message-ID: <4D3E88F0.3090301@gmail.com> (raw)
In-Reply-To: <AANLkTikQEd_5phELfTM_j+8v6SWchw3q_h2KSctE7M88@mail.gmail.com>

On 01/25/2011 12:32 AM, Mike Frysinger wrote:
> On Mon, Jan 24, 2011 at 16:44, Stefano Bonifazi wrote:
>>>    http://lists.gnu.org/archive/html/qemu-devel/2010-07/msg01626.html
>> A noob question, how can I get your sources? Is there a simpler solution
>> than "copy&paste" all the code from your messages into patches and then
>> applying them? Can you just send your sources by email? Or can I download
>> them from a site?
> weird ... usually the gnu archives have a "download raw text" option
> so you can get a mbox file to import into your mailer
>
> you could use the gmane.org nntp gateway to get all the raw e-mails though:
>      nntp://news.gmane.org/gmane.comp.emulators.qemu
> -mike
Hi!
I didn't mean the messages sources, I am already using nntp with 
thunderbird, I meant whether there is an option for getting the .c, .h 
sources, instead of copying the patches and apply them .. sorry but I am 
really new with this
Thank you!
Regards!
Stefano B.

  reply	other threads:[~2011-01-25  8:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 11:34 [Qemu-devel] qemu-user: relocating target code weakness Stefano Bonifazi
2011-01-24 16:29 ` Mulyadi Santosa
2011-01-24 18:16   ` Stefano Bonifazi
2011-01-24 20:00     ` Mike Frysinger
2011-01-24 20:58       ` Stefano Bonifazi
2011-01-24 21:21         ` Mike Frysinger
2011-01-24 21:52           ` Stefano Bonifazi
2011-01-24 22:11             ` Mike Frysinger
2011-01-24 22:24               ` Stefano Bonifazi
2011-01-24 22:34                 ` Mike Frysinger
2011-01-25  0:06   ` Mike Frysinger
2011-01-25  0:18     ` Mike Frysinger
2011-01-25  8:49       ` Stefano Bonifazi
2011-01-25  8:26     ` Stefano Bonifazi
2011-01-24 19:46 ` Richard Henderson
2011-01-24 21:44   ` Stefano Bonifazi
2011-01-24 23:32     ` Mike Frysinger
2011-01-25  8:25       ` Stefano Bonifazi [this message]
2011-01-25  1:36     ` Richard Henderson
2011-01-25  8:47       ` Stefano Bonifazi
2011-01-25  8:53         ` Mike Frysinger
2011-01-25  9:58           ` Stefano Bonifazi
2011-01-25 10:47           ` Stefano Bonifazi
2011-01-25 16:22             ` Richard Henderson
2011-01-25 19:03               ` Stefano Bonifazi
2011-01-25 11:06           ` Stefano Bonifazi
2011-01-25 16:26             ` Richard Henderson
2011-01-25 19:49               ` Stefano Bonifazi
2011-01-25 20:53                 ` Lluís
2011-01-26 11:07       ` Stefano Bonifazi
2011-01-26 15:38         ` Richard Henderson
2011-01-26 17:44           ` Stefano Bonifazi
2011-01-26 20:17           ` Lluís
2011-01-26 20:19             ` Richard Henderson
2011-01-26 20:33               ` Stefano Bonifazi
2011-01-26 20:36               ` Lluís

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=4D3E88F0.3090301@gmail.com \
    --to=stefboombastic@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=vapier.adi@gmail.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.