1. 08 9月, 2006 1 次提交
  2. 28 8月, 2006 1 次提交
  3. 09 8月, 2006 1 次提交
  4. 07 8月, 2006 1 次提交
  5. 04 8月, 2006 1 次提交
  6. 07 7月, 2006 1 次提交
  7. 03 7月, 2006 1 次提交
    • J
      autoconf: Use autoconf to write installation directories to config.mak.autogen · 55667714
      Jakub Narebski 提交于
      This is beginning of patch series introducing installation configuration
      using autoconf (and no other autotools) to git. The idea is to generate
      config.mak.autogen using ./configure (generated from configure.ac by running
      autoconf) from config.mak.in, so one can use autoconf as an _alternative_ to
      ordinary Makefile, and creating one's own config.mak. Local settings in
      config.mak override generated settings in config.mak.autogen
      
      This patch includes minimal configure.ac and config.mak.in, so one can set
      installation directories using autoconf generated ./configure script
      e.g. ./configure --prefix=/usr
      Signed-off-by: NJakub Narebski <jnareb@gmail.com>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      55667714
  8. 02 7月, 2006 1 次提交
    • E
      Add git-instaweb, instantly browse the working repo with gitweb · a51d37c1
      Eric Wong 提交于
      I got tired of having to configure gitweb for every repository
      I work on.  I sometimes prefer gitweb to standard GUIs like gitk
      or gitview; so this lets me automatically configure gitweb to
      browse my working repository and also opens my browser to it.
      
      Updates from the original patch:
      
      Added Apache/mod_perl2 compatibility if Dennis Stosberg's gitweb
      has been applied, too: <20060621130708.Gcbc6e5c@leonov.stosberg.net>
      
      General cleanups in shell code usage.
      Signed-off-by: NEric Wong <normalperson@yhbt.net>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      a51d37c1
  9. 23 6月, 2006 1 次提交
  10. 21 6月, 2006 1 次提交
  11. 25 5月, 2006 1 次提交
  12. 23 5月, 2006 1 次提交
  13. 28 4月, 2006 1 次提交
  14. 24 4月, 2006 1 次提交
  15. 20 4月, 2006 2 次提交
    • J
      git-update-index --unresolve · 2bd452d3
      Junio C Hamano 提交于
      Retire git-unresolve and make it into "git-update-index --unresolve".
      It processes all paths that follow.
      
      During a merge, you would mark a path that is dealt with with:
      
      	$ git update-index hello
      
      and you would "undo" it with:
      
      	$ git update-index --unresolve hello
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      2bd452d3
    • J
      Add git-unresolve <paths>... · ec167793
      Junio C Hamano 提交于
      This is an attempt to address the issue raised on #git channel
      recently by Carl Worth.
      
      After a conflicted automerge, "git diff" shows a combined diff
      to give you how the tentative automerge result differs from
      what came from each branch.  During a complex merge, it is
      tempting to be able to resolve a few paths at a time, mark
      them "I've dealt with them" with git-update-index to unclutter
      the next "git diff" output, and keep going.  However, when the
      final result does not compile or otherwise found to be a
      mismerge, the workflow to fix the mismerged paths suddenly
      changes to "git diff HEAD -- path" (to get a diff from our
      HEAD before merging) and "git diff MERGE_HEAD -- path" (to get
      a diff from theirs), and it cannot show the combined anymore.
      
      With git-unresolve <paths>..., the versions from our branch and
      their branch for specified blobs are placed in stage #2 and
      stage #3, without touching the working tree files.  This gives
      you the combined diff back for easier review, along with
      "diff --ours" and "diff --theirs".
      
      One thing it does not do is to place the base in stage #1; this
      means "diff --base" would behave differently between the run
      immediately after a conflicted three-way merge, and the run
      after an update-index by mistake followed by a git-unresolve.
      
      We could theoretically run merge-base between HEAD and
      MERGE_HEAD to find which tree to place in stage #1, but
      reviewing "diff --base" is not that useful so....
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      ec167793
  16. 15 4月, 2006 1 次提交
  17. 05 4月, 2006 1 次提交
  18. 27 3月, 2006 1 次提交
  19. 11 3月, 2006 1 次提交
    • M
      Add git-imap-send, derived from isync 1.0.1. · f2561fda
      Mike McCormack 提交于
      git-imap-send drops a patch series generated by git-format-patch into an
      IMAP folder. This allows patch submitters to send patches through their
      own mail program.
      
      git-imap-send uses the following values from the GIT repository
      configuration:
      
      The target IMAP folder:
      
      [imap]
               Folder = "INBOX.Drafts"
      
      A command to open an ssh tunnel to the imap mail server.
      
      [imap]
               Tunnel = "ssh -q user@imap.server.com /usr/bin/imapd ./Maildir
      2> /dev/null"
      
      [imap]
               Host = imap.server.com
               User = bob
               Password = pwd
               Port = 143
      f2561fda
  20. 10 3月, 2006 1 次提交
  21. 06 3月, 2006 1 次提交
  22. 25 2月, 2006 1 次提交
  23. 23 2月, 2006 1 次提交
    • C
      Add new git-rm command with documentation · d4a1cab5
      Carl Worth 提交于
      This adds a git-rm command which provides convenience similar to
      git-add, (and a bit more since it takes care of the rm as well if
      given -f).
      
      Like git-add, git-rm expands the given path names through
      git-ls-files. This means it only acts on files listed in the
      index. And it does act recursively on directories by default, (no -r
      needed as in the case of rm itself). When it recurses, it does not
      remove empty directories that are left behind.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      d4a1cab5
  24. 08 2月, 2006 1 次提交
  25. 06 2月, 2006 1 次提交
    • J
      git-show · 80d48ac6
      Junio C Hamano 提交于
      This is essentially 'git whatchanged -n1 --always --cc "$@"'.
      Just like whatchanged takes default flags from
      whatchanged.difftree configuration, this uses show.difftree
      configuration.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      80d48ac6
  26. 11 1月, 2006 1 次提交
  27. 06 1月, 2006 1 次提交
  28. 28 12月, 2005 1 次提交
  29. 20 12月, 2005 1 次提交
    • J
      Remove "octopus". · e32faa8a
      Junio C Hamano 提交于
      We still advertise "git resolve" as a standalone command, but never
      "git octopus", so nobody should be using it and it is safe to
      retire it.  The functionality is still available as a strategy
      backend.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      e32faa8a
  30. 25 11月, 2005 1 次提交
  31. 20 11月, 2005 1 次提交
  32. 14 11月, 2005 1 次提交
  33. 13 11月, 2005 1 次提交
  34. 12 11月, 2005 3 次提交
  35. 08 11月, 2005 1 次提交
  36. 04 11月, 2005 1 次提交
    • J
      Add 'ours' merge strategy. · 64da9e60
      Junio C Hamano 提交于
      This adds the coolest merge strategy ever, "ours".  It can take
      arbitrary number of foreign heads and merge them into the
      current branch, with the resulting tree always taken from our
      branch head, hence its name.
      
      What this means is that you can declare that the current branch
      supersedes the development histories of other branches using
      this merge strategy.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      64da9e60
  37. 28 10月, 2005 1 次提交