1. 09 5月, 2006 1 次提交
  2. 04 4月, 2006 1 次提交
  3. 03 4月, 2006 1 次提交
  4. 30 3月, 2006 1 次提交
    • J
      tree/diff header cleanup. · 1b0c7174
      Junio C Hamano 提交于
      Introduce tree-walk.[ch] and move "struct tree_desc" and
      associated functions from various places.
      
      Rename DIFF_FILE_CANON_MODE(mode) macro to canon_mode(mode) and
      move it to cache.h.  This macro returns the canonicalized
      st_mode value in the host byte order for files, symlinks and
      directories -- to be compared with a tree_desc entry.
      create_ce_mode(mode) in cache.h is similar but is intended to be
      used for index entries (so it does not work for directories) and
      returns the value in the network byte order.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      1b0c7174
  5. 26 3月, 2006 5 次提交
  6. 24 3月, 2006 1 次提交
  7. 04 3月, 2006 1 次提交
    • J
      tar-tree: file/dirmode fix. · 473d404b
      Junio C Hamano 提交于
      This fixes two bugs introduced when we switched to generic tree
      traversal code.
      
       (1) directory mode recorded silently became 0755, not 0777
      
       (2) if passed a tree object (not a commit), it emitted an
           alarming error message (but proceeded anyway).
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      473d404b
  8. 01 2月, 2006 1 次提交
  9. 31 1月, 2006 2 次提交
  10. 08 1月, 2006 1 次提交
  11. 20 12月, 2005 1 次提交
  12. 29 11月, 2005 1 次提交
  13. 02 10月, 2005 1 次提交
  14. 10 8月, 2005 1 次提交
    • T
      [PATCH] -Werror fixes · 4ec99bf0
      Timo Sirainen 提交于
      GCC's format __attribute__ is good for checking errors, especially
      with -Wformat=2 parameter. This fixes most of the reported problems
      against 2005-08-09 snapshot.
      4ec99bf0
  15. 30 7月, 2005 1 次提交
  16. 22 6月, 2005 1 次提交
  17. 03 6月, 2005 2 次提交
  18. 21 5月, 2005 1 次提交
    • L
      sparse cleanup · e99d59ff
      Linus Torvalds 提交于
      Fix various things that sparse complains about:
       - use NULL instead of 0
       - make sure we declare everything properly, or mark it static
       - use proper function declarations ("fn(void)" instead of "fn()")
      
      Sparse is always right.
      e99d59ff
  19. 20 5月, 2005 1 次提交
  20. 18 5月, 2005 1 次提交
  21. 10 5月, 2005 1 次提交
  22. 07 5月, 2005 7 次提交
  23. 02 5月, 2005 1 次提交
    • L
      Add "get_sha1()" helper function. · 3c249c95
      Linus Torvalds 提交于
      This allows the programs to use various simplified versions of
      the SHA1 names, eg just say "HEAD" for the SHA1 pointed to by
      the .git/HEAD file etc.
      
      For example, this commit has been done with
      
      	git-commit-tree $(git-write-tree) -p HEAD
      
      instead of the traditional "$(cat .git/HEAD)" syntax.
      3c249c95
  24. 30 4月, 2005 1 次提交
  25. 29 4月, 2005 2 次提交
    • R
      [PATCH] Use read_object_with_reference() in tar-tree · db413479
      Rene Scharfe 提交于
      This patch replaces the usage of read_tree_with_tree_or_commit_sha1()
      with read_object_with_reference() in tar-tree.  As a result the code
      that tries to figure out the commit time doesn't need to open the commit
      object 'by hand' any more.
      
      Signed-off-by: Rene Scharfe <lsrfire.ath.cx>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      db413479
    • R
      [PATCH] create tar archives of tree on the fly · 731ab9cc
      Rene Scharfe 提交于
      This is an improved version of tar-tree, a streaming archive creator for
      GIT.  The major added feature is blocking; all write(2) calls now have a
      size of 10240, just as GNU tar (and tape drives) likes them.  The
      buffering overhead does not seem to degrade performance because most
      files in the repositories I tested this with are smaller than 10KB, so
      we need fewer system calls. 
      
      File names are still restricted to 500 bytes and the archive format
      currently only allows for files up to 8GB.  Both restrictions can be
      lifted if need be with more pax extended headers. 
      
      The archive format used is the pax interchange format, i.e.  POSIX tar
      format.  It can be read by (and created with) GNU tar.  If I read the
      specs correctly tar-tree should now be standards compliant (modulo
      bugs). 
      
      Because it streams the archive (think ls-tree merged with cat-file),
      tar-tree doesn't need to create any temporary files.  That makes it
      quite fast. 
      
      It accepts tree IDs and commit IDs as first parameter.  In the latter
      case tar-tree tries to get the commit date out of the committer line. 
      Else all files in the archive are time-stamped with the current time. 
      
      An optional second parameter is used as a path prefix for all files in
      the archive.  Example:
      
         $ tar-tree a2755a80f40e5794ddc20e00f781af9d6320fafb \
         linux-2.6.12-rc3 | bzip9 -9 > linux-2.6.12-rc3.tar.bz2
      Signed-off-by: NRene Scharfe <rene.scharfe@lsrfire.ath.cx>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      731ab9cc