1. 15 7月, 2006 4 次提交
  2. 14 7月, 2006 16 次提交
  3. 13 7月, 2006 10 次提交
  4. 12 7月, 2006 8 次提交
  5. 11 7月, 2006 2 次提交
    • S
      Log ref changes made by git-fetch and git-pull. · 55b7835e
      Shawn Pearce 提交于
      When git-fetch updates a reference record in the associated reflog
      what type of update took place and who caused it (git-fetch or
      git-pull, by invoking git-fetch).
      Signed-off-by: NShawn O. Pearce <spearce@spearce.org>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      55b7835e
    • S
      Record the type of commit operation in the reflog. · a3a733e6
      Shawn Pearce 提交于
      If committing a merge (.git/MERGE_HEAD exists), an initial tree
      (no HEAD) or using --amend to amend the prior commit then denote
      the subtype of commit in the reflog.  This helps to distinguish
      amended or merge commits from normal commits.
      
      In the case of --amend the prior sha1 is probably the commit which
      is being thrown away in favor of the new commit.  Since it is likely
      that the old commit doesn't have any ref pointing to it anymore
      it can be interesting to know why that the commit was replaced
      and orphaned.
      
      In the case of a merge the prior sha1 is probably the first parent
      of the new merge commit.  Consequently having its prior sha1 in the
      reflog is slightly less interesting but its still informative to
      know the commit was the result of a merge which had to be completed
      by hand.
      Signed-off-by: NShawn O. Pearce <spearce@spearce.org>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      a3a733e6