1. 12 1月, 2006 1 次提交
  2. 18 11月, 2005 1 次提交
    • R
      [NET]: Sanitize NET_SCHED protection in /net/sched/Kconfig · 05b8b0fa
      Roman Zippel 提交于
      On Thu, 17 Nov 2005, David Gómez wrote:
      
      > I found out that if i select NET_CLS_ROUTE4, save my changes and exit
      > menuconfig, execute again make menuconfig and go to QoS options, then the new
      > available options are visible. So menuconfig has some problem refreshing
      > contents :?
      
      No, they were there before too, but you have to go up one level to see 
      them.
      
      It's better in 2.6.15-rc1-git5, but the menu structure is still a little 
      messed up, the patch below properly indents all menu entries.
      Signed-off-by: NRoman Zippel <zippel@linux-m68k.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      05b8b0fa
  3. 03 11月, 2005 1 次提交
  4. 14 10月, 2005 1 次提交
  5. 30 8月, 2005 1 次提交
  6. 12 7月, 2005 1 次提交
    • S
      [NET]: move config options out to individual protocols · 6a2e9b73
      Sam Ravnborg 提交于
      Move the protocol specific config options out to the specific protocols.
      With this change net/Kconfig now starts to become readable and serve as a
      good basis for further re-structuring.
      
      The menu structure is left almost intact, except that indention is
      fixed in most cases. Most visible are the INET changes where several
      "depends on INET" are replaced with a single ifdef INET / endif pair.
      
      Several new files were created to accomplish this change - they are
      small but serve the purpose that config options are now distributed
      out where they belongs.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6a2e9b73
  7. 25 6月, 2005 1 次提交
  8. 24 6月, 2005 2 次提交
  9. 09 6月, 2005 1 次提交
  10. 04 5月, 2005 1 次提交
  11. 25 4月, 2005 1 次提交
  12. 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