1. 30 4月, 2014 1 次提交
  2. 30 3月, 2012 1 次提交
  3. 04 4月, 2011 1 次提交
    • A
      eradicate bashisms in scripts/patch-kernel · 177525d2
      Andreas Mohr 提交于
      Silence a remaining annoying (or worse, irritating - "is my entire patched tree
      broken now!?") bashism-related message that occurs when /bin/sh is configured
      to instead deploy dash, a POSIX-compliant shell, as is the pretty much
      standard case on e.g. Debian.
      
      Current kernel version is 2.6.38 ( Flesh-Eating Bats with Fangs)
      ===>  linux-2.6.38.patch-kernel_test/scripts/patch-kernel: line 253: [: =: unary operator expected  <===
      cannot find patch file: patch-2.6.39
      Signed-off-by: NAndreas Mohr <andi@lisas.de>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      177525d2
  4. 07 8月, 2008 1 次提交
  5. 29 1月, 2008 1 次提交
    • A
      kbuild: eradicate bashisms in scripts/patch-kernel · 22d6a6a0
      Andreas Mohr 提交于
      Make the patch-kernel shell script sufficiently compatible with POSIX
      shells, i.e., remove bashisms from scripts/patch-kernel.
      This means that it now also works on dash 0.5.3-5
      and still works on bash 3.1dfsg-8.
      
      Full changelog:
      - replaced non-standard "==" by standard "="
      - replaced non-standard "source" statement by POSIX "dot" command
      - use leading ./ on mktemp filename to force the tempfile to a local
        directory, so that the search path is not used
      - replace bash syntax to remove leading dot by similar POSIX syntax
      - added missing (optional/not required) $ signs to shell variable names
      Signed-off-by: NAndreas Mohr <andi@lisas.de>
      Acked-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      22d6a6a0
  6. 03 1月, 2006 1 次提交
  7. 06 5月, 2005 1 次提交
  8. 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