Skip to content
Snippets Groups Projects
  1. Apr 04, 2011
    • Andreas Mohr's avatar
      eradicate bashisms in scripts/patch-kernel · 177525d2
      Andreas Mohr authored
      
      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: default avatarAndreas Mohr <andi@lisas.de>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      177525d2
  2. Aug 06, 2008
  3. Jan 28, 2008
    • Andreas Mohr's avatar
      kbuild: eradicate bashisms in scripts/patch-kernel · 22d6a6a0
      Andreas Mohr authored
      
      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: default avatarAndreas Mohr <andi@lisas.de>
      Acked-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      22d6a6a0
  4. Jan 03, 2006
  5. May 05, 2005
  6. Apr 16, 2005
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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
Loading