1. 01 8月, 2006 1 次提交
  2. 31 7月, 2006 1 次提交
  3. 29 7月, 2006 1 次提交
  4. 27 7月, 2006 1 次提交
  5. 26 7月, 2006 2 次提交
  6. 15 7月, 2006 1 次提交
  7. 09 7月, 2006 3 次提交
  8. 04 7月, 2006 1 次提交
  9. 28 6月, 2006 3 次提交
  10. 19 6月, 2006 6 次提交
  11. 17 6月, 2006 1 次提交
    • J
      fix git alias · d8498500
      Junio C Hamano 提交于
      When extra command line arguments are given to a command that
      was alias-expanded, the code generated a wrong argument list,
      leaving the original alias in the result, and forgetting to
      terminate the new argv list.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      d8498500
  12. 11 6月, 2006 1 次提交
  13. 06 6月, 2006 2 次提交
  14. 04 6月, 2006 1 次提交
  15. 25 5月, 2006 1 次提交
  16. 24 5月, 2006 8 次提交
  17. 21 5月, 2006 1 次提交
  18. 20 5月, 2006 3 次提交
    • J
      built-in tar-tree and remote tar-tree · 21754264
      Junio C Hamano 提交于
      This makes tar-tree a built-in.  As an added bonus, you can now
      say:
      
      	git tar-tree --remote=remote-repository <ent> [<base>]
      
      This does not work with git-daemon yet, but should work with
      localhost and git over ssh transports.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      21754264
    • L
      Add builtin "git rm" command · d9b814cc
      Linus Torvalds 提交于
      This changes semantics very subtly, because it adds a new atomicity
      guarantee.
      
      In particular, if you "git rm" several files, it will now do all or
      nothing. The old shell-script really looped over the removed files one by
      one, and would basically randomly fail in the middle if "-f" was used and
      one of the files didn't exist in the working directory.
      
      This C builtin one will not re-write the index after each remove, but
      instead remove all files at once. However, that means that if "-f" is used
      (to also force removal of the file from the working directory), and some
      files have already been removed from the workspace, it won't stop in the
      middle in some half-way state like the old one did.
      
      So what happens is that if the _first_ file fails to be removed with "-f",
      we abort the whole "git rm". But once we've started removing, we don't
      leave anything half done. If some of the other files don't exist, we'll
      just ignore errors of removal from the working tree.
      
      This is only an issue with "-f", of course.
      
      I think the new behaviour is strictly an improvement, but perhaps more
      importantly, it is _different_. As a special case, the semantics are
      identical for the single-file case (which is the only one our test-suite
      seems to test).
      
      The other question is what to do with leading directories. The old "git
      rm" script didn't do anything, which is somewhat inconsistent. This one
      will actually clean up directories that have become empty as a result of
      removing the last file, but maybe we want to have a flag to decide the
      behaviour?
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      d9b814cc
    • T
      Builtin git-init-db · c3c8835f
      Timo Hirvonen 提交于
      Basically this just renames init-db.c to builtin-init-db.c and makes
      some strings const.
      Signed-off-by: NTimo Hirvonen <tihirvon@gmail.com>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      c3c8835f
  19. 19 5月, 2006 2 次提交