qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "André Braga" <meianoite@gmail.com>
To: Hetz Ben Hamo <hetz@witch.dyndns.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patches please
Date: Sat, 31 Jul 2004 01:44:30 -0300	[thread overview]
Message-ID: <2ad73a04073021442299acea@mail.gmail.com> (raw)
In-Reply-To: <200407310229.03219.hetz@kde.org>

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

Here's the patch I mentioned 2 days ago. It enables one to customize
some optimization flags (namely CFLAGS, HELPER_CFLAGS and OP_CFLAGS)
by setting them in the environment (as usual! ;D).

To be honest, it does some superfluous things, but I'll leave it up to
Fabrice to refactor the makefiles to fit his taste (hence the
"unusual" -albeit valid- patch format: so humans can quickly pinpoint
the differences).

Sorry about the delay, but real life kicks in sometimes ;)


-- 
"No, no, you're not thinking; you're just being logical"
Niels Bohr



On Sat, 31 Jul 2004 02:29:03 +0300, Hetz Ben Hamo <hetz@kde.org> wrote:
> Hi,
> 
> Due to excessive emails I got (tons of viruses etc) I seems lost few patches..
> 
> So I'm asking - does anyone has a patch that  it's not in my web site and want
> it to be considered for committing?
> 
> if so, please do the follwing things:
> 
> Create a tarball with 2 files:
> 
> * A README file which explains what the patch does, how to apply and how to
> use
> * the patch (unified please) itself.
> * A suggestion for a directory name (if you want to)
> 
> Fabrice will be back soon to the QEMU scene, and its your chance to get your
> patch in and get the fame (girls will be around you, luxury cars ;)
> 
> Thanks for helping,
> Hetz

[-- Attachment #2: customflags.tar.gz --]
[-- Type: application/x-gzip, Size: 1763 bytes --]

      reply	other threads:[~2004-07-31  4:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 23:29 [Qemu-devel] Patches please Hetz Ben Hamo
2004-07-31  4:44 ` André Braga [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=2ad73a04073021442299acea@mail.gmail.com \
    --to=meianoite@gmail.com \
    --cc=hetz@witch.dyndns.org \
    --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).