linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Olaf Hering <olh@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cc-version not available to change EXTRA_CFLAGS
Date: Sun, 22 Jan 2006 00:25:42 +0100	[thread overview]
Message-ID: <20060121232542.GA19480@mars.ravnborg.org> (raw)
In-Reply-To: <20060121231539.GA23789@suse.de>

On Sun, Jan 22, 2006 at 12:15:39AM +0100, Olaf Hering wrote:
> Will you include the reiserfs change with a check for earlier then 4.0
> or 4.1 or should I send a separate patch?

Please submit as a separate patch. I try to keep non-kbuild stuff out of
the kbuild tree. This make is less confusing.

I will not commit this until sometime tomorrow - I have to set up
something so I can track bugfixes and enhancements in parallel.
This is 2.6.17 material IMO in kbuild land except if we want this in for
reiserfs before 2.6.17.

I try to be rather strict about bug-fixes versus enhancements in kbuild.
The latest unexpected breakage shows how easy it is to introduce
unexpected errors in someones build :-(

	Sam

  reply	other threads:[~2006-01-21 23:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 18:08 cc-version not available to change EXTRA_CFLAGS Olaf Hering
2006-01-21 22:12 ` Sam Ravnborg
2006-01-21 22:21   ` Olaf Hering
2006-01-21 22:57 ` Sam Ravnborg
2006-01-21 23:15   ` Olaf Hering
2006-01-21 23:25     ` Sam Ravnborg [this message]
2006-01-23 11:02       ` Olaf Hering
2006-02-10 19:47   ` Olaf Hering
2006-02-18  9:03     ` Sam Ravnborg
2006-07-19  9:02 ` Olaf Hering
2006-07-23 17:51   ` Sam Ravnborg
2006-01-21 19:07 Andrey Borzenkov
2006-01-21 19:11 ` Olaf Hering
2006-01-21 19:47   ` Andrey Borzenkov
2006-01-21 21:07     ` Olaf Hering
2006-01-21 22:51 ` Jan Engelhardt
2006-01-21 23:00 ` Sam Ravnborg

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=20060121232542.GA19480@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    /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).