Skip to content

G
git

李少辉-开发者 / git
与 Fork 源项目一致

从无法访问的项目Fork

通知 2
Star 1
Fork 0
G
git

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 16 8月, 2014 1 次提交
  3. 06 8月, 2014 1 次提交
  5. 31 7月, 2014 1 次提交
  7. 24 7月, 2014 2 次提交
  9. 17 7月, 2014 1 次提交
  11. 14 7月, 2014 3 次提交
    • K
      git: add performance tracing for git's main() function to debug scripts · 578da039
      由 Karsten Blees 提交于 
      Use trace_performance to measure and print execution time and command line
arguments of the entire main() function. In constrast to the shell's 'time'
utility, which measures total time of the parent process, this logs all
involved git commands recursively. This is particularly useful to debug
performance issues of scripted commands (i.e. which git commands were
called with which parameters, and how long did they execute).

Due to git's deliberate use of exit(), the implementation uses an atexit
routine rather than just adding trace_performance_since() at the end of
main().

Usage example: > GIT_TRACE_PERFORMANCE=~/git-trace.log git stash list

Creates a log file like this:
23:57:38.638765 trace.c:405 performance: 0.000310107 s: git command: 'git' 'rev-parse' '--git-dir'
23:57:38.644387 trace.c:405 performance: 0.000261759 s: git command: 'git' 'rev-parse' '--show-toplevel'
23:57:38.646207 trace.c:405 performance: 0.000304468 s: git command: 'git' 'config' '--get-colorbool' 'color.interactive'
23:57:38.648491 trace.c:405 performance: 0.000241667 s: git command: 'git' 'config' '--get-color' 'color.interactive.help' 'red bold'
23:57:38.650465 trace.c:405 performance: 0.000243063 s: git command: 'git' 'config' '--get-color' '' 'reset'
23:57:38.654850 trace.c:405 performance: 0.025126313 s: git command: 'git' 'stash' 'list'
Signed-off-by: NKarsten Blees <blees@dcon.de>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      578da039
    • K
      sha1_file: change GIT_TRACE_PACK_ACCESS logging to use trace API · 67dc598e
      由 Karsten Blees 提交于 
      This changes GIT_TRACE_PACK_ACCESS functionality as follows:
 * supports the same options as GIT_TRACE (e.g. printing to stderr)
 * no longer supports relative paths
 * appends to the trace file rather than overwriting
Signed-off-by: NKarsten Blees <blees@dcon.de>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      67dc598e
    • K
      Documentation/git.txt: improve documentation of 'GIT_TRACE*' variables · eb9250df
      由 Karsten Blees 提交于 
      Separate GIT_TRACE description into what it prints and how to configure
where trace output is printed to. Change other GIT_TRACE_* descriptions to
refer to GIT_TRACE.

Add descriptions for GIT_TRACE_SETUP and GIT_TRACE_SHALLOW.
Signed-off-by: NKarsten Blees <blees@dcon.de>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      eb9250df
  13. 26 6月, 2014 1 次提交
  15. 31 5月, 2014 1 次提交
  17. 29 5月, 2014 1 次提交
  19. 22 5月, 2014 1 次提交
  21. 10 5月, 2014 1 次提交
  23. 10 4月, 2014 1 次提交
  25. 19 3月, 2014 1 次提交
    • J
      Git 1.9.1 · cee0c275
      由 Junio C Hamano 提交于 
      The version numbering scheme has changed since Git 1.9 and we
dropped the third dewey-decimal from the traditional numbering
(e.g. both 1.8.4 and 1.8.5 were major feature releases).  This
release 1.9.1 is the first maintenance relase for Git 1.9.
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      cee0c275
  27. 25 2月, 2014 1 次提交
  29. 15 2月, 2014 1 次提交
  31. 14 2月, 2014 1 次提交
  33. 06 2月, 2014 1 次提交
  35. 14 1月, 2014 1 次提交
  37. 18 12月, 2013 1 次提交
  39. 07 12月, 2013 1 次提交
    • Z
      difftool: display the number of files in the diff queue in the prompt · ee7fb0b1
      由 Zoltan Klinger 提交于 
      When --prompt option is set, git-difftool displays a prompt for each
modified file to be viewed in an external diff program.  At that
point, it could be useful to display a counter and the total number
of files in the diff queue.

Below is the current difftool prompt for the first of 5 modified files:

    Viewing: 'diff.c'
    Launch 'vimdiff' [Y/n]:

Consider the modified prompt:

    Viewing (1/5): 'diff.c'
    Launch 'vimdiff' [Y/n]:

The current GIT_EXTERNAL_DIFF mechanism does not tell the number of
paths in the diff queue nor the current counter.  To make this
"counter/total" info available for GIT_EXTERNAL_DIFF programs
without breaking existing ones by doing the following:

 - Keep track of the number of paths shown so far in diff_options;

 - Export two new environment variables from run_external_diff() to
   show the total number of paths (from diff_queue_struct) and the
   current value of the counter (from diff_options); and

 - Update git-difftool--helper to use these two environment variables.
Signed-off-by: NZoltan Klinger <zoltan.klinger@gmail.com>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      ee7fb0b1
  41. 04 12月, 2013 1 次提交
  43. 03 12月, 2013 1 次提交
  45. 28 11月, 2013 1 次提交
  47. 21 11月, 2013 1 次提交
  49. 09 11月, 2013 1 次提交
  51. 29 10月, 2013 1 次提交
  53. 16 10月, 2013 1 次提交
  55. 27 9月, 2013 1 次提交
  57. 10 9月, 2013 1 次提交
    • N
      git: run in a directory given with -C option · 44e1e4d6
      由 Nazri Ramliy 提交于 
      This is similar in spirit to "make -C dir ..." and "tar -C dir ...".

It takes more keypresses to invoke git command in a different
directory without leaving the current directory:

    1. (cd ~/foo && git status)
       git --git-dir=~/foo/.git --work-dir=~/foo status
       GIT_DIR=~/foo/.git GIT_WORK_TREE=~/foo git status
    2. (cd ../..; git grep foo)
    3. for d in d1 d2 d3; do (cd $d && git svn rebase); done

The methods shown above are acceptable for scripting but are too
cumbersome for quick command line invocations.

With this new option, the above can be done with fewer keystrokes:

    1. git -C ~/foo status
    2. git -C ../.. grep foo
    3. for d in d1 d2 d3; do git -C $d svn rebase; done

A new test script is added to verify the behavior of this option with
other path-related options like --git-dir and --work-tree.
Signed-off-by: NNazri Ramliy <ayiehere@gmail.com>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      44e1e4d6
  59. 24 8月, 2013 1 次提交
  61. 14 8月, 2013 1 次提交
    • J
      core-tutorial: trim the section on Inspecting Changes · 627a8b8d
      由 Junio C Hamano 提交于 
      Back when the core tutorial was written, `log` and `whatchanged`
were scripted Porcelains.  In the "Inspecting Changes" section that
talks about the plumbing commands in the diff family, it made sense
to use `log` and `whatchanged` as good examples of the use of these
plumbing commands, and because even these scripted Porcelains were
novelty (there wasn't the new end-user tutorial written), it made
some sense to illustrate uses of the `git log` (and `git
whatchanged`) scripted Porcelain commands.

But we no longer have scripted `log` and `whatchanged` to serve as
examples, and this document is not where the end users learn what
`git log` command is about.  Stop at briefly mentioning the
possibility of combining rev-list with diff-tree to build your own
log, and leave the end-user documentation of `log` to the new
tutorial and the user manual.

Also resurrect the last version of `git-log`, `git-whatchanged`, and
`git-show` to serve as examples to contrib/examples/ directory.

While at it, remove 'whatchanged' from a list of sample commands
that are affected by GIT_FLUSH environment variable. This is not
meant to be an exhaustive list but as a list of typical ones, and an
old command that is kept primarily for backward compatibility does
not belong to it.
Helped-by: NMatthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      627a8b8d
  63. 23 7月, 2013 1 次提交
  65. 16 7月, 2013 4 次提交
  67. 29 6月, 2013 1 次提交