1. 31 3月, 2009 8 次提交
  2. 01 1月, 2009 1 次提交
  3. 14 11月, 2008 1 次提交
  4. 23 10月, 2008 1 次提交
  5. 28 4月, 2008 1 次提交
  6. 31 3月, 2008 1 次提交
  7. 09 5月, 2007 1 次提交
  8. 13 2月, 2007 1 次提交
  9. 09 12月, 2006 1 次提交
  10. 04 10月, 2006 1 次提交
  11. 01 10月, 2006 3 次提交
  12. 01 7月, 2006 1 次提交
  13. 03 3月, 2006 1 次提交
  14. 02 2月, 2006 1 次提交
  15. 15 1月, 2006 1 次提交
  16. 14 8月, 2005 1 次提交
  17. 13 7月, 2005 1 次提交
    • L
      reiserfs: run scripts/Lindent on reiserfs code · bd4c625c
      Linus Torvalds 提交于
      This was a pure indentation change, using:
      
      	scripts/Lindent fs/reiserfs/*.c include/linux/reiserfs_*.h
      
      to make reiserfs match the regular Linux indentation style.  As Jeff
      Mahoney <jeffm@suse.com> writes:
      
       The ReiserFS code is a mix of a number of different coding styles, sometimes
       different even from line-to-line. Since the code has been relatively stable
       for quite some time and there are few outstanding patches to be applied, it
       is time to reformat the code to conform to the Linux style standard outlined
       in Documentation/CodingStyle.
      
       This patch contains the result of running scripts/Lindent against
       fs/reiserfs/*.c and include/linux/reiserfs_*.h. There are places where the
       code can be made to look better, but I'd rather keep those patches separate
       so that there isn't a subtle by-hand hand accident in the middle of a huge
       patch. To be clear: This patch is reformatting *only*.
      
       A number of patches may follow that continue to make the code more consistent
       with the Linux coding style.
      
       Hans wasn't particularly enthusiastic about these patches, but said he
       wouldn't really oppose them either.
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      bd4c625c
  18. 24 6月, 2005 1 次提交
  19. 06 5月, 2005 1 次提交
  20. 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