1. 01 6月, 2010 1 次提交
  2. 29 5月, 2010 4 次提交
  3. 26 5月, 2010 4 次提交
  4. 21 5月, 2010 3 次提交
  5. 20 5月, 2010 1 次提交
  6. 19 5月, 2010 4 次提交
  7. 12 5月, 2010 1 次提交
  8. 11 5月, 2010 1 次提交
    • J
      handle "git --bare init <dir>" properly · 87a074df
      Jeff King 提交于
      If we know we are creating a bare repository, we use setenv
      to set the GIT_DIR directory to the current directory
      (either where we already were, or one we created and chdir'd
      into with "git init --bare <dir>").
      
      However, with "git --bare init <dir>" (note the --bare as a
      git wrapper option), the setup code actually sets GIT_DIR
      for us, but it uses the wrong, original cwd when a directory
      is given. Because our setenv does not use the overwrite
      flag, it is ignored.
      
      We need to set the overwrite flag, but only when we are
      given a directory on the command line. That still allows:
      
        GIT_DIR=foo.git git init --bare
      
      to work. The behavior is changed for:
      
        GIT_DIR=foo.git git init --bare bar.git
      
      which used to create the repository in foo.git, but now will
      use bar.git. This is more sane, as command line options
      should generally override the environment.
      
      Noticed by Oliver Hoffmann.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      87a074df
  9. 09 5月, 2010 2 次提交
  10. 08 5月, 2010 1 次提交
  11. 07 5月, 2010 1 次提交
    • J
      test-lib: some shells do not let $? propagate into an eval · b6b0afdc
      Jonathan Nieder 提交于
      In 3bf78867 (test-lib: Let tests specify commands to be run at end of
      test, 2010-05-02), the git test harness learned to run cleanup
      commands unconditionally at the end of a test.  During each test,
      the intended cleanup actions are collected in the test_cleanup variable
      and evaluated.  That variable looks something like this:
      
      	eval_ret=$?; clean_something && (exit "$eval_ret")
      	eval_ret=$?; clean_something_else && (exit "$eval_ret")
      	eval_ret=$?; final_cleanup && (exit "$eval_ret")
      	eval_ret=$?
      
      All cleanup actions are run unconditionally but if one of them fails
      it is properly reported through $eval_ret.
      
      On FreeBSD, unfortunately, $? is set at the beginning of an ‘eval’
      to 0 instead of the exit status of the previous command.  This results
      in tests using test_expect_code appearing to fail and all others
      appearing to pass, unless their cleanup fails.  Avoid the problem by
      setting eval_ret before the ‘eval’ begins.
      
      Thanks to Jeff King for the explanation.
      
      Cc: Jeff King <peff@peff.net>
      Cc: Johannes Sixt <j6t@kdbg.org>
      Acked-by: NJeff King <peff@peff.net>
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      b6b0afdc
  12. 05 5月, 2010 6 次提交
  13. 02 5月, 2010 5 次提交
  14. 24 4月, 2010 3 次提交
  15. 23 4月, 2010 3 次提交