Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001558]: make saveconfig rewrite .conf file incorrect
Date: Tue, 30 Oct 2007 13:14:57 -0700	[thread overview]
Message-ID: <960dd21760c0a440d5018a4066a93e7b@busybox.net> (raw)


The following issue has been RESOLVED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1558 
====================================================================== 
Reported By:                mata
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1558
Category:                   Other
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             10-28-2007 02:56 PDT
Last Modified:              10-30-2007 13:14 PDT
====================================================================== 
Summary:                    make saveconfig rewrite .conf file incorrect
Description: 
When do `make saveconfig`, config files will be copied to local/proj/, and
at main .config file uClibc,buildroot,kernel config location are
overrided.
But when check with `make menuconfig`, those config file location are
erased. I chased this process. At finally, I found `saveconfig`
modification are not for mconf format.
This patch is for override mconf acceptable format at saveconfig.
====================================================================== 

---------------------------------------------------------------------- 
 UlfSamuelsson - 10-30-07 13:14  
---------------------------------------------------------------------- 
Patch applied in rev 20335 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-28-07 02:56  mata           New Issue                                    
10-28-07 02:56  mata           Status                   new => assigned     
10-28-07 02:56  mata           Assigned To               => buildroot       
10-28-07 02:56  mata           File Added: project.diff                     
10-30-07 13:14  UlfSamuelsson  Status                   assigned => resolved
10-30-07 13:14  UlfSamuelsson  Resolution               open => fixed       
10-30-07 13:14  UlfSamuelsson  Note Added: 0002878                          
======================================================================

             reply	other threads:[~2007-10-30 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 20:14 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-30 21:45 [Buildroot] [buildroot 0001558]: make saveconfig rewrite .conf file incorrect bugs at busybox.net
2007-10-28  9:56 bugs at busybox.net

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=960dd21760c0a440d5018a4066a93e7b@busybox.net \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /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