1. 11 Apr, 2016 1 commit
  2. 31 Mar, 2016 2 commits
  3. 23 Mar, 2016 3 commits
  4. 17 Sep, 2015 1 commit
    • git_futils_mkdir_*: make a relative-to-base mkdir · ac2fba0e
      Untangle git_futils_mkdir from git_futils_mkdir_ext - the latter
      assumes that we own everything beneath the base, as if it were
      being called with a base of the repository or working directory,
      and is tailored towards checkout and ensuring that there is no
      bogosity beneath the base that must be cleaned up.
      
      This is (at best) slow and (at worst) unsafe in the larger context
      of a filesystem where we do not own things and cannot do things like
      unlink symlinks that are in our way.
      Edward Thomson committed
  5. 13 Sep, 2015 1 commit
  6. 30 Aug, 2015 1 commit
  7. 22 Jun, 2015 1 commit
    • diff: check files with the same or newer timestamps · ff475375
      When a file on the workdir has the same or a newer timestamp than the
      index, we need to perform a full check of the contents, as the update of
      the file may have happened just after we wrote the index.
      
      The iterator changes are such that we can reach inside the workdir
      iterator from the diff, though it may be better to have an accessor
      instead of moving these structs into the header.
      Carlos Martín Nieto committed
  8. 20 Jun, 2015 1 commit
  9. 16 Jun, 2015 1 commit
  10. 02 Jun, 2015 1 commit
  11. 28 May, 2015 4 commits
  12. 20 May, 2015 1 commit
  13. 04 May, 2015 1 commit
  14. 17 Apr, 2015 1 commit
  15. 03 Mar, 2015 2 commits
  16. 05 Dec, 2014 1 commit
  17. 23 Nov, 2014 1 commit
  18. 09 Nov, 2014 1 commit
  19. 07 Nov, 2014 2 commits
  20. 06 Nov, 2014 1 commit
  21. 05 Nov, 2014 1 commit
  22. 13 Aug, 2014 1 commit
  23. 08 Aug, 2014 2 commits
    • Demonstrate a trailing slash failure. · bbe13802
      `git help ignore` has this to say about trailing slashes:
      
      > If the pattern ends with a slash, it is removed for the purpose of
      > the following description, but it would only find a match with a
      > directory. In other words, foo/ will match a directory foo and
      > paths underneath it, but will not match a regular file or a
      > symbolic link foo (this is consistent with the way how pathspec
      > works in general in Git).
      
      Sure enough, having manually performed the same steps as this test,
      `git status` tells us the following:
      
      	# On branch master
      	#
      	# Initial commit
      	#
      	# Changes to be committed:
      	#   (use "git rm --cached <file>..." to unstage)
      	#
      	#	new file:   force.txt
      	#
      	# Untracked files:
      	#   (use "git add <file>..." to include in what will be committed)
      	#
      	#	../.gitignore
      	#	child1/
      	#	child2/
      
      i.e. neither child1 nor child2 is ignored.
      Rob Rix committed
    • status: failing test with slash-star · aa5cdf63
      When writing 'bin/*' in the rules, this means we ignore very file inside
      bin/ individually, but do not ignore the directory itself. Thus the
      status listing should list both files under bin/, one untracked and one
      ignored.
      Carlos Martín Nieto committed
  24. 01 Jul, 2014 1 commit
  25. 04 Jun, 2014 2 commits
  26. 30 May, 2014 2 commits
  27. 22 May, 2014 2 commits
  28. 21 May, 2014 1 commit