Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org,
	Greg KH <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH] scripts/config: properly report and set string options
Date: Tue, 10 Apr 2012 08:57:53 -0500	[thread overview]
Message-ID: <20120410135753.GB2444@burratino> (raw)
In-Reply-To: <201204091802.29839.yann.morin.1998@free.fr>

Yann E. MORIN wrote:

>   - it breaks the build for users that tweak the kernel configuration from
>     an upper-layer (aka 'integrated') build-system, using this script which
>     is bundled with the kernel in the first place.

The questions I have are, did using special characters like this work
before or is support for values with quotes inside just a new feature?
Or is there some wrapper around the linux makefile that automatically
uses values with quotes on them, making it effectively impossible for
some class of people to run some versions of Linux?

I don't expect this patch to cause problems for people, but it is a
good practice to explain what scenario justifies backporting a patch
to the stable series, if only because it keeps the volume of patches
to search through when there is a new bug down.

Thanks,
Jonathan

  parent reply	other threads:[~2012-04-10 13:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 12:49 [PATCH] scripts/config: properly report and set string options Yann E. MORIN
2012-04-09 13:22 ` Yann E. MORIN
2012-04-09 14:04 ` Andi Kleen
2012-04-09 15:30 ` Greg KH
2012-04-09 16:02   ` Yann E. MORIN
2012-04-10  8:57     ` Michal Marek
2012-04-10 13:57     ` Jonathan Nieder [this message]
2012-04-10 23:07       ` Yann E. MORIN
2012-04-11  1:33         ` Jonathan Nieder
2012-04-19 21:07 ` Yann E. MORIN
2012-05-15 22:14   ` Michal Marek
2012-05-09 21:27 ` Yann E. MORIN

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=20120410135753.GB2444@burratino \
    --to=jrnieder@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=stable@vger.kernel.org \
    --cc=yann.morin.1998@free.fr \
    /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