1. 15 11月, 2014 1 次提交
  2. 29 10月, 2014 1 次提交
  3. 28 10月, 2014 1 次提交
  4. 08 10月, 2014 5 次提交
  5. 30 9月, 2014 8 次提交
  6. 28 9月, 2014 1 次提交
  7. 26 9月, 2014 3 次提交
  8. 23 9月, 2014 1 次提交
  9. 20 9月, 2014 13 次提交
  10. 17 9月, 2014 2 次提交
    • S
      Documentation/git-rebase.txt: <upstream> must be given to specify <branch> · 95c68267
      Sergey Organov 提交于
      Current syntax description makes one wonder if there is any
      syntactic way to distinguish between <branch> and <upstream> so that
      one can specify <branch> but not <upstream>, but that is not the
      case.
      
      Make it explicit that these arguments are positional, i.e. the
      earlier ones cannot be omitted if you want to give later ones.
      Signed-off-by: NSergey Organov <sorganov@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      95c68267
    • J
      mailinfo: make ">From" in-body header check more robust · 2da1f366
      Jeff King 提交于
      Since commit 81c5cf78 (mailinfo: skip bogus UNIX From line inside
      body, 2006-05-21), we have treated lines like ">From" in the body as
      headers. This makes "git am" work for people who erroneously paste
      the whole output from format-patch:
      
        From 12345abcd...fedcba543210 Mon Sep 17 00:00:00 2001
        From: them
        Subject: [PATCH] whatever
      
      into their email body (assuming that an mbox writer then quotes
      "From" as ">From", as otherwise we would actually mailsplit on the
      in-body line).
      
      However, this has false positives if somebody actually has a commit
      body that starts with "From "; in this case we erroneously remove
      the line entirely from the commit message. We can make this check
      more robust by making sure the line actually looks like a real mbox
      "From" line.
      
      Inspect the line that begins with ">From " a more carefully to only
      skip lines that match the expected pattern (note that the datestamp
      part of the format-patch output is designed to be kept constant to
      help those who write magic(5) entries).
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      2da1f366
  11. 13 9月, 2014 1 次提交
    • J
      fsck: return non-zero status on missing ref tips · 30d1038d
      Jeff King 提交于
      Fsck tries hard to detect missing objects, and will complain
      (and exit non-zero) about any inter-object links that are
      missing. However, it will not exit non-zero for any missing
      ref tips, meaning that a severely broken repository may
      still pass "git fsck && echo ok".
      
      The problem is that we use for_each_ref to iterate over the
      ref tips, which hides broken tips. It does at least print an
      error from the refs.c code, but fsck does not ever see the
      ref and cannot note the problem in its exit code. We can solve
      this by using for_each_rawref and noting the error ourselves.
      
      In addition to adding tests for this case, we add tests for
      all types of missing-object links (all of which worked, but
      which we were not testing).
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      30d1038d
  12. 12 9月, 2014 1 次提交
  13. 11 9月, 2014 1 次提交
  14. 04 9月, 2014 1 次提交