1. 08 2月, 2011 1 次提交
  2. 23 2月, 2010 1 次提交
    • L
      Move 'builtin-*' into a 'builtin/' subdirectory · 81b50f3c
      Linus Torvalds 提交于
      This shrinks the top-level directory a bit, and makes it much more
      pleasant to use auto-completion on the thing. Instead of
      
      	[torvalds@nehalem git]$ em buil<tab>
      	Display all 180 possibilities? (y or n)
      	[torvalds@nehalem git]$ em builtin-sh
      	builtin-shortlog.c     builtin-show-branch.c  builtin-show-ref.c
      	builtin-shortlog.o     builtin-show-branch.o  builtin-show-ref.o
      	[torvalds@nehalem git]$ em builtin-shor<tab>
      	builtin-shortlog.c  builtin-shortlog.o
      	[torvalds@nehalem git]$ em builtin-shortlog.c
      
      you get
      
      	[torvalds@nehalem git]$ em buil<tab>		[type]
      	builtin/   builtin.h
      	[torvalds@nehalem git]$ em builtin		[auto-completes to]
      	[torvalds@nehalem git]$ em builtin/sh<tab>	[type]
      	shortlog.c     shortlog.o     show-branch.c  show-branch.o  show-ref.c     show-ref.o
      	[torvalds@nehalem git]$ em builtin/sho		[auto-completes to]
      	[torvalds@nehalem git]$ em builtin/shor<tab>	[type]
      	shortlog.c  shortlog.o
      	[torvalds@nehalem git]$ em builtin/shortlog.c
      
      which doesn't seem all that different, but not having that annoying
      break in "Display all 180 possibilities?" is quite a relief.
      
      NOTE! If you do this in a clean tree (no object files etc), or using an
      editor that has auto-completion rules that ignores '*.o' files, you
      won't see that annoying 'Display all 180 possibilities?' message - it
      will just show the choices instead.  I think bash has some cut-off
      around 100 choices or something.
      
      So the reason I see this is that I'm using an odd editory, and thus
      don't have the rules to cut down on auto-completion.  But you can
      simulate that by using 'ls' instead, or something similar.
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      81b50f3c
  3. 22 1月, 2010 1 次提交
  4. 28 6月, 2009 1 次提交
    • T
      Use die_errno() instead of die() when checking syscalls · 0721c314
      Thomas Rast 提交于
      Lots of die() calls did not actually report the kind of error, which
      can leave the user confused as to the real problem.  Use die_errno()
      where we check a system/library call that sets errno on failure, or
      one of the following that wrap such calls:
      
        Function              Passes on error from
        --------              --------------------
        odb_pack_keep         open
        read_ancestry         fopen
        read_in_full          xread
        strbuf_read           xread
        strbuf_read_file      open or strbuf_read_file
        strbuf_readlink       readlink
        write_in_full         xwrite
      Signed-off-by: NThomas Rast <trast@student.ethz.ch>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      0721c314
  5. 25 5月, 2009 1 次提交
  6. 01 3月, 2009 1 次提交
  7. 26 1月, 2009 1 次提交
  8. 12 11月, 2008 1 次提交
  9. 13 10月, 2008 1 次提交
  10. 04 8月, 2008 5 次提交
  11. 14 7月, 2008 1 次提交
    • S
      Make usage strings dash-less · 1b1dd23f
      Stephan Beyer 提交于
      When you misuse a git command, you are shown the usage string.
      But this is currently shown in the dashed form.  So if you just
      copy what you see, it will not work, when the dashed form
      is no longer supported.
      
      This patch makes git commands show the dash-less version.
      
      For shell scripts that do not specify OPTIONS_SPEC, git-sh-setup.sh
      generates a dash-less usage string now.
      Signed-off-by: NStephan Beyer <s-beyer@gmx.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      1b1dd23f
  12. 24 5月, 2008 1 次提交
  13. 15 5月, 2008 1 次提交
  14. 23 2月, 2008 1 次提交
    • G
      hash-object: cleanup handling of command line options · 8a2f5e5b
      Gerrit Pape 提交于
      git hash-object used to process the --stdin command line argument
      before reading subsequent arguments.  This caused 'git hash-object
      --stdin -w' to fail to actually write the object into the
      database, while '-w --stdin' properly did.  Now git hash-object
      first reads all arguments, and then processes them.
      
      This regresses one insane use case.  git hash-object used to allow
      multiple --stdin arguments on the command line:
      
         $ git hash-object --stdin --stdin
           foo
           ^D
           bar
           ^D
      
      Now git hash-object errors out if --stdin is given more than once.
      
      Reported by Josh Triplett through
       http://bugs.debian.org/464432Signed-off-by: NGerrit Pape <pape@smarden.org>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      8a2f5e5b
  15. 11 11月, 2007 1 次提交
  16. 01 3月, 2007 2 次提交
  17. 04 8月, 2006 1 次提交
  18. 04 4月, 2006 1 次提交
  19. 11 12月, 2005 1 次提交
  20. 06 12月, 2005 1 次提交
    • J
      hash-object: -- and --help · 9c2e7c0c
      Junio C Hamano 提交于
      It was cumbersome to feed hash-object the file '-t' (you could
      have said "./-t", though).  Teach it '--' that terminates the
      option list, like everybody else.  There is no way to extract
      usage string from the command either, so teach it "--help" as
      well.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      9c2e7c0c
  21. 29 11月, 2005 2 次提交
  22. 30 7月, 2005 1 次提交
  23. 09 7月, 2005 1 次提交