1. 26 10月, 2007 3 次提交
  2. 18 10月, 2007 1 次提交
  3. 13 10月, 2007 1 次提交
  4. 17 7月, 2007 1 次提交
    • S
      kconfig: fix update-po-config · b70e325c
      Sam Ravnborg 提交于
      Massimo Maiurana <maiurana@gmail.com> reported that
      update-po-config was broken:
      1) spelling errors in Makefile so arch/um failed
      2) UTF-8 was not supported
      
      The following patch address the above problems.
      kxgettext now append the output to the .pot file
      generated by xgettext - so we have a header.
      In all places UFT-8 is specifed so we now flawlessly
      support UTF-8.
      The Kconfig files had an empty string in a few cases -
      these are now supressed in kxgettext.
      
      With this the translators can now pick up where they left
      and get it all translated.
      There are ~11000 strings to be translated...
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc:  Massimo Maiurana <maiurana@gmail.com>
      Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
      b70e325c
  5. 03 5月, 2007 2 次提交
  6. 30 9月, 2006 3 次提交
    • S
      kbuild: do not build mconf & lxdialog unless needed · c29121b7
      Sam Ravnborg 提交于
      Due to a limitation in kbuild all objects referred
      by xxx-y or xxx-objs will be build when one of
      the targets needs to e build.
      
      This caused lxdialog to be build pulling in ncurses
      that is not always available.
      So avoid building mconf & lxdialog unless really needed.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      c29121b7
    • S
      kconfig/lxdialog: fix make mrproper · 903947d2
      Sam Ravnborg 提交于
      No Makefile in scripts/kconfig/lxdialog anymore, so do not
      go there during make mrproper.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      903947d2
    • S
      kconfig/menuconfig: lxdialog is now built-in · 2982de69
      Sam Ravnborg 提交于
      lxdialog was previously called as an external program causing screen
      to flicker when used. With this patch lxdialog is now built-in.
      It is loosly based om previous work by:  Petr Baudis <pasky@ucw.cz>
      
      Following is a list of changes:
      o Moved build of dialog routings to kconfig Makefile
      o menubox + checklist uses a new item list to hold all menu items
      o in util.c implmented helper function to deal with item list
      o menubox now uses parameters to save scroll state (avoids temp file)
      o textbox now get text to be displayed as parameter and not a file
      o make sure to properly delete subwin's before main windows
      o killed unused files: lxdialog.c msgbox.c
      o modified return value for ESC to match direct calling
      o in a few places the code has been adjusted to 80 char wide
      o in textbox a small refactoring was made to make code remotely readable
      o in mconf removed all unused stuff (functions/variables)
      
      Following is a list of know short comings:
      a) pressing ESC twice will be interpreted as two ESC presses
      b) resize does not work. menuconfig needs to be restarted to be adjusted
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      2982de69
  7. 25 9月, 2006 1 次提交
  8. 06 3月, 2006 1 次提交
  9. 27 2月, 2006 1 次提交
  10. 10 2月, 2006 1 次提交
  11. 06 2月, 2006 1 次提交
  12. 07 1月, 2006 1 次提交
  13. 17 12月, 2005 1 次提交
  14. 23 11月, 2005 1 次提交
  15. 09 11月, 2005 2 次提交
  16. 07 11月, 2005 1 次提交
  17. 06 11月, 2005 1 次提交
  18. 31 10月, 2005 1 次提交
  19. 05 9月, 2005 1 次提交
  20. 06 5月, 2005 1 次提交
    • A
      [PATCH] Kconfig i18n support · 3b9fa093
      Arnaldo Carvalho de Melo 提交于
      This patch adds i18n support for make *config, allowing users to have the
      config process in their own language.
      
      No printk was harmed in the process, don't worry, so all the bug reports,
      kernel messages, etc, remain in english, just the user tools to configure
      the kernel are internationalized.
      
      Users not interested in translations can just unset the related LANG,
      LC_ALL, etc env variables and have the config process in plain english,
      something like:
      
      LANG= make menuconfig
      
      is enough for having the whole config process in english. Or just don't
      install any translation file.
      
      Translations for brazilian portuguese are being done by a team of
      volunteers at:
      
      http://www.visionflex.inf.br/kernel_ptbr/pmwiki.php/Principal/Traducoes
      
      To start the translation process:
      
        make update-po-config
      
        This will generate the pot template named scripts/kconfig/linux.pot,
        copy it to, say, ~/es.po, to start the translation for spanish.
      
      To test your translation, as root issue this command:
      
        msgfmt -o /usr/share/locale/es/LC_MESSAGES/linux.mo ~/es.po
      
        Replace "es" with your language code.
      
        Then execute, for instance:
      
        make menuconfig
      
      The current patch doesn't use any optimization to reduce the size of the
      generated .mo file, it is possible to use the config option as a key, but
      this doesn't prevent the current patch from being used or the translations
      done under the current scheme to be in any way lost if we chose to do any
      kind of keying.
      
      Thanks to Fabricio Vaccari for starting the pt_BR (brazilian portuguese)
      translation effort, Thiago Maciera for helping me with the gconf.cc (QT
      frontent) i18n coding and to all the volunteers that are already working on
      the first translation, to pt_BR.
      
      I left the question on whether to ship the translations with the stock kernel
      sources to be discussed here, please share your suggestions.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@conectiva.com.br>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: Linus Torvalds <torvalds@osdl.org
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      3b9fa093
  21. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4