1. 04 1月, 2009 1 次提交
  2. 22 12月, 2008 1 次提交
  3. 20 12月, 2008 7 次提交
  4. 17 12月, 2008 4 次提交
  5. 16 12月, 2008 1 次提交
  6. 15 12月, 2008 2 次提交
    • J
      pager: do not dup2 stderr if it is already redirected · a8335024
      Junio C Hamano 提交于
      An earlier commit 61b80509 (sending errors to stdout under $PAGER,
      2008-02-16) avoided losing the error messages that are sent to the
      standard error when $PAGER is in effect by dup2'ing fd 2 to the pager.
      his way, showing a tag object that points to a bad object:
      
          $ git show tag-foo
      
      would give the error message to the pager.  However, it was not quite
      right if the user did:
      
          $ git show 2>error.log tag-foo
      
      i.e. use the pager but store the errors in a separate file.
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      a8335024
    • J
      git-show: do not segfault when showing a bad tag · d2dadfe8
      Junio C Hamano 提交于
      When a tag points at a bad or nonexistent object, we should diagnose the
      breakage and exit.  An earlier commit 4f3dcc27 (Fix 'git show' on signed
      tag of signed tag of commit, 2008-07-01) lost this check and made it
      segfault instead; not good.
      
      This fixes it.
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      d2dadfe8
  7. 13 12月, 2008 1 次提交
  8. 11 12月, 2008 2 次提交
  9. 10 12月, 2008 1 次提交
    • J
      work around Python warnings from AsciiDoc · aa971cb9
      Junio C Hamano 提交于
      It appears that a reference to an anchor defined as [[anchor-name]] from
      another place using <<anchor-name>> syntax, when the anchor name contains
      a string "-with-" in its name, triggers these warnings from Python
      interpreter.
      
        asciidoc -b docbook -d book user-manual.txt
        <string>:1: Warning: 'with' will become a reserved keyword in Python 2.6
        <string>:1: Warning: 'with' will become a reserved keyword in Python 2.6
        <string>:1: Warning: 'with' will become a reserved keyword in Python 2.6
        <string>:1: Warning: 'with' will become a reserved keyword in Python 2.6
      
      There currently is no reference to "Finding comments with given content",
      but for consistency and for futureproofing, the anchor is also updated as
      the other ones that are actually used and trigger these warnings.
      Signed-off-by: NJunio C Hamano <junio@pobox.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      aa971cb9
  10. 09 12月, 2008 1 次提交
    • D
      git-svn: Make following parents atomic · 553589f7
      Deskin Miller 提交于
      find_parent_branch generates branch@rev type branches when one has to
      look back through SVN history to properly get the history for a branch
      copied from somewhere not already being tracked by git-svn.  If in the
      process of fetching this history, git-svn is interrupted, then when one
      fetches again, it will use whatever was last fetched as the parent
      commit and fail to fetch any more history which it didn't get to before
      being terminated.  This is especially troubling in that different
      git-svn copies of the same SVN repository can end up with different
      commit sha1s, incorrectly showing the history as divergent and
      precluding easy collaboration using git push and fetch.
      
      To fix this, when we initialise the Git::SVN object $gs to search for
      and perhaps fetch history, we check if there are any commits in SVN in
      the range between the current revision $gs is at, and the top revision
      for which we were asked to fill history.  If there are commits we're
      missing in that range, we continue the fetch from the current revision
      to the top, properly getting all history before using it as the parent
      for the branch we're trying to create.
      Signed-off-by: NDeskin Miller <deskinm@umich.edu>
      Acked-by: NEric Wong <normalperson@yhbt.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      553589f7
  11. 08 12月, 2008 2 次提交
  12. 07 12月, 2008 4 次提交
  13. 03 12月, 2008 5 次提交
  14. 01 12月, 2008 4 次提交
  15. 28 11月, 2008 4 次提交
    • J
      Merge branch 'mv/fast-export' into maint · 539eec48
      Junio C Hamano 提交于
      * mv/fast-export:
        fast-export: use an unsorted string list for extra_refs
        Add new testcase to show fast-export does not always exports all tags
      539eec48
    • S
      sha1_file.c: resolve confusion EACCES vs EPERM · 35243577
      Sam Vilain 提交于
      An earlier commit 916d081b (Nicer error messages in case saving an object
      to db goes wrong, 2006-11-09) confused EACCES with EPERM, the latter of
      which is an unlikely error from mkstemp().
      Signed-off-by: NSam Vilain <sam@vilain.net>
      35243577
    • J
      sha1_file: avoid bogus "file exists" error message · 65117abc
      Joey Hess 提交于
      This avoids the following misleading error message:
      
      error: unable to create temporary sha1 filename ./objects/15: File exists
      
      mkstemp can fail for many reasons, one of which, ENOENT, can occur if
      the directory for the temp file doesn't exist. create_tmpfile tried to
      handle this case by always trying to mkdir the directory, even if it
      already existed. This caused errno to be clobbered, so one cannot tell
      why mkstemp really failed, and it truncated the buffer to just the
      directory name, resulting in the strange error message shown above.
      
      Note that in both occasions that I've seen this failure, it has not been
      due to a missing directory, or bad permissions, but some other, unknown
      mkstemp failure mode that did not occur when I ran git again. This code
      could perhaps be made more robust by retrying mkstemp, in case it was a
      transient failure.
      Signed-off-by: NJoey Hess <joey@kitenet.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      65117abc
    • M
      git checkout: don't warn about unborn branch if -f is already passed · 1510dbe3
      Matt McCutchen 提交于
      I think it's unnecessary to warn that the checkout has been forced due to an
      unborn current branch if -f has been explicitly passed.  For one project, I am
      using git-new-workdir to create workdirs from a bare repository whose HEAD is
      set to an unborn branch, and this warning started to irritate me.
      Signed-off-by: NMatt McCutchen <matt@mattmccutchen.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      1510dbe3