All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hiromu Yakura <hiromu1996@gmail.com>
Subject: Re: [PATCH] xconfig: merge code path to conf_write()
Date: Mon, 25 Jul 2011 23:24:51 +0200	[thread overview]
Message-ID: <4E2DDF23.8050806@suse.cz> (raw)
In-Reply-To: <CACqU3MXmMejkTuUPqWQZH6BSXp6q_B5QuVNZbNjU=3s4sukagg@mail.gmail.com>

On 25.7.2011 17:25, Arnaud Lacombe wrote:
> Hi Michal,
> 
> On Mon, Jul 25, 2011 at 9:53 AM, Michal Marek <mmarek@suse.cz> wrote:
>> On 25.5.2011 15:18, Michal Marek wrote:
>>>
>>> The following patch avoids the data loss if the configuration cannot be
>>> saved.
>>>
>>> Michal
>>>
>>> Subject: [PATCH] xconfig: Abort close if configuration cannot be saved
>>>
>>> Give the user an opportunity to fix the error or save the configuration
>>> under a different path.
>>>
>>> Reported-by: Hiromu Yakura<hiromu1996@gmail.com>
>>> Signed-off-by: Michal Marek<mmarek@suse.cz>
>>
>> I completely forgot about this patch. It's applied now and will be in 3.1.
>>
> gni ? isn't this issue already fixed by
> https://patchwork.kernel.org/patch/812862/ which went in v3.0 ??

That's the prerequisite. This patch makes sure that xconfig does not
exit if the save failed.

Michal

      reply	other threads:[~2011-07-25 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 18:16 [PATCH] xconfig: merge code path to conf_write() Arnaud Lacombe
2011-05-25 13:18 ` Michal Marek
2011-07-25 13:53   ` Michal Marek
2011-07-25 15:25     ` Arnaud Lacombe
2011-07-25 21:24       ` Michal Marek [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=4E2DDF23.8050806@suse.cz \
    --to=mmarek@suse.cz \
    --cc=hiromu1996@gmail.com \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.