All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Josh Triplett <josh@freedesktop.org>
Cc: Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
	Junio C Hamano <junkio@cox.net>,
	GIT Mailing-list <git@vger.kernel.org>,
	linux-sparse@vger.kernel.org
Subject: Re: [RFC][PATCH 00/10] Sparse: Git's "make check" target
Date: Sun, 10 Jun 2007 00:56:30 +0200	[thread overview]
Message-ID: <20070609225630.GC3008@uranus.ravnborg.org> (raw)
In-Reply-To: <466A5204.6060200@freedesktop.org>

> 
> Also, you might consider just using cgcc to run both GCC and Sparse.  That
> would handle the issue of target-specific CFLAGS, by ensuring that Sparse and
> GCC always see the same CFLAGS.

Is this the recommended way?
I that case I suggest that someone looks into the linux kernel part
and change it to use this method.

	Sam

  reply	other threads:[~2007-06-09 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 22:06 [RFC][PATCH 00/10] Sparse: Git's "make check" target Ramsay Jones
2007-06-09  7:08 ` Josh Triplett
2007-06-09 22:56   ` Sam Ravnborg [this message]
2007-06-09 23:50     ` Josh Triplett
2007-06-12 17:37   ` Ramsay Jones
2007-06-13 20:25     ` Josh Triplett

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=20070609225630.GC3008@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=git@vger.kernel.org \
    --cc=josh@freedesktop.org \
    --cc=junkio@cox.net \
    --cc=linux-sparse@vger.kernel.org \
    --cc=ramsay@ramsay1.demon.co.uk \
    /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.