1. 12 2月, 2008 1 次提交
  2. 29 1月, 2008 2 次提交
  3. 15 1月, 2008 1 次提交
    • J
      Fix git-rerere documentation · 11c57e6a
      Junio C Hamano 提交于
      rerere.enabled is _not_ on by default.  The command is enabled if rr-cache
      exists even when rerere.enabled is missing, and enabled or disabled by
      explicitly setting the rerere.enabled variable.
      11c57e6a
  4. 12 1月, 2008 1 次提交
  5. 08 1月, 2008 1 次提交
  6. 07 1月, 2008 2 次提交
    • J
      Document the color.interactive semantics · 47ee06f1
      Jeff King 提交于
      There are two possible confusions with the color.interactive
      description:
      
        1. the short name "interactive" implies that it covers all
           interactive commands; let's explicitly make it so, even
           though there are no other interactive commands which
           currently use it
      
        2. Not all parts of "git add --interactive" are controlled
           by color.interactive (specifically, the diffs require
           tweaking color.diff). So let's clarify that it applies
           only to displays and prompts.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      47ee06f1
    • D
      Documentation: rename gitlink macro to linkgit · 5162e697
      Dan McGee 提交于
      Between AsciiDoc 8.2.2 and 8.2.3, the following change was made to the stock
      Asciidoc configuration:
      
      @@ -149,7 +153,10 @@
       # Inline macros.
       # Backslash prefix required for escape processing.
       # (?s) re flag for line spanning.
      -(?su)[\\]?(?P<name>\w(\w|-)*?):(?P<target>\S*?)(\[(?P<attrlist>.*?)\])=
      +
      +# Explicit so they can be nested.
      +(?su)[\\]?(?P<name>(http|https|ftp|file|mailto|callto|image|link)):(?P<target>\S*?)(\[(?P<attrlist>.*?)\])=
      +
       # Anchor: [[[id]]]. Bibliographic anchor.
       (?su)[\\]?\[\[\[(?P<attrlist>[\w][\w-]*?)\]\]\]=anchor3
       # Anchor: [[id,xreflabel]]
      
      This default regex now matches explicit values, and unfortunately in this
      case gitlink was being matched by just 'link', causing the wrong inline
      macro template to be applied. By renaming the macro, we can avoid being
      matched by the wrong regex.
      Signed-off-by: NDan McGee <dpmcgee@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      5162e697
  7. 01 1月, 2008 1 次提交
  8. 19 12月, 2007 1 次提交
  9. 18 12月, 2007 1 次提交
  10. 17 12月, 2007 1 次提交
  11. 08 12月, 2007 1 次提交
  12. 06 12月, 2007 2 次提交
    • J
      Color support for "git-add -i" · b4c61ed6
      Junio C Hamano 提交于
      This is mostly lifted from earlier series by Dan Zwell, but updated to
      use "git config --get-color" and "git config --get-colorbool" to make it
      simpler and more consistent with commands written in C.
      
      A new configuration color.interactive variable is like color.diff and
      color.status, and controls if "git-add -i" uses color.
      
      A set of configuration variables, color.interactive.<slot>, are used to
      define what color is used for the prompt, header, and help text.
      
      For perl scripts, Git.pm provides $repo->get_color() method, which takes
      the slot name and the default color, and returns the terminal escape
      sequence to color the output text.  $repo->get_colorbool() method can be
      used to check if color is set to be used for a given operation.
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      b4c61ed6
    • J
      Documentation: color.* = true means "auto" · cec99d8c
      Junio C Hamano 提交于
      We forgot to document the earlier sanity-fix.
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      cec99d8c
  13. 04 12月, 2007 3 次提交
  14. 29 11月, 2007 1 次提交
    • J
      Teach 'git pull' about --rebase · cd67e4d4
      Johannes Schindelin 提交于
      When calling 'git pull' with the '--rebase' option, it performs a
      fetch + rebase instead of a fetch + merge.
      
      This behavior is more desirable than fetch + pull when a topic branch
      is ready to be submitted and needs to be update.
      
      fetch + rebase might also be considered a better workflow with shared
      repositories in any case, or for contributors to a centrally managed
      repository, such as WINE's.
      
      As a convenience, you can set the default behavior for a branch by
      defining the config variable branch.<name>.rebase, which is
      interpreted as a bool.  This setting can be overridden on the command
      line by --rebase and --no-rebase.
      Signed-off-by: NJohannes Schindelin <johannes.schindelin@gmx.de>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      cd67e4d4
  15. 25 11月, 2007 1 次提交
    • J
      core.whitespace: documentation updates. · 91af7ae5
      Junio C Hamano 提交于
      This adds description of core.whitespace to the manual page of git-config,
      and updates the stale description of whitespace handling in the manual
      page of git-apply.
      
      Also demote "strip" to a synonym status for "fix" as the value of --whitespace
      option given to git-apply.
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      91af7ae5
  16. 20 11月, 2007 2 次提交
  17. 04 11月, 2007 2 次提交
  18. 02 11月, 2007 1 次提交
  19. 16 10月, 2007 1 次提交
  20. 03 10月, 2007 1 次提交
  21. 24 9月, 2007 1 次提交
    • L
      git-merge: add support for branch.<name>.mergeoptions · aec7b362
      Lars Hjemli 提交于
      This enables per branch configuration of merge options. Currently, the most
      useful options to specify per branch are --squash, --summary/--no-summary
      and possibly --strategy, but all options are supported.
      
      Note: Options containing whitespace will _not_ be handled correctly. Luckily,
      the only option which can include whitespace is --message and it doesn't
      make much sense to give that option a default value.
      Signed-off-by: NLars Hjemli <hjemli@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      aec7b362
  22. 19 9月, 2007 1 次提交
    • D
      Make fetch a builtin · b888d61c
      Daniel Barkalow 提交于
      Thanks to Johannes Schindelin for review and fixes, and Julian
      Phillips for the original C translation.
      
      This changes a few small bits of behavior:
      
      branch.<name>.merge is parsed as if it were the lhs of a fetch
      refspec, and does not have to exactly match the actual lhs of a
      refspec, so long as it is a valid abbreviation for the same ref.
      
      branch.<name>.merge is no longer ignored if the remote is configured
      with a branches/* file. Neither behavior is useful, because there can
      only be one ref that gets fetched, but this is more consistant.
      
      Also, fetch prints different information to standard out.
      Signed-off-by: NDaniel Barkalow <barkalow@iabervon.org>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      b888d61c
  23. 18 9月, 2007 2 次提交
  24. 11 9月, 2007 1 次提交
  25. 01 9月, 2007 2 次提交
    • J
      Documentation: minor AsciiDoc mark-up fixes. · f368f5a6
      Junio C Hamano 提交于
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      f368f5a6
    • J
      git-diff: resurrect the traditional empty "diff --git" behaviour · aecbf914
      Junio C Hamano 提交于
      The warning message to suggest "Consider running git-status" from
      "git-diff" that we experimented with during the 1.5.3 cycle turns
      out to be a bad idea.  It robbed cache-dirty information from people
      who valued it, while still asking users to run "update-index --refresh".
      It was hoped that the new behaviour would at least have some educational
      value, but not showing the cache-dirty paths like before meant that the
      user would not even know easily which paths were cache-dirty, and it
      made the need to refresh the index look like even more unnecessary chore.
      
      This commit reinstates the traditional behaviour, but with a twist.
      
      By default, the empty "diff --git" output is totally squelched out
      from "git diff" output.  At the end of the command, it automatically
      runs "update-index --refresh" as needed, without even bothering the
      user.  In other words, people who do not care about the cache-dirtyness
      do not even have to see the warning.
      
      The traditional behaviour to see the stat-dirty output and to bypassing
      the overhead of content comparison can be specified by setting the
      configuration variable diff.autorefreshindex to false.
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      aecbf914
  26. 25 8月, 2007 2 次提交
  27. 23 8月, 2007 1 次提交
  28. 20 8月, 2007 1 次提交
  29. 03 8月, 2007 1 次提交
  30. 27 7月, 2007 1 次提交