Skip to content

G
git

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

从无法访问的项目Fork

通知 2
Star 1
Fork 0
G
git

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

切换分支/标签
  1. 13 1月, 2010 1 次提交
  3. 29 11月, 2009 1 次提交
  5. 23 11月, 2009 2 次提交
  7. 21 11月, 2009 1 次提交
  9. 20 11月, 2009 1 次提交
  11. 18 11月, 2009 1 次提交
  13. 17 11月, 2009 1 次提交
  15. 14 11月, 2009 1 次提交
  17. 10 11月, 2009 1 次提交
  19. 05 11月, 2009 1 次提交
    • S
      Smart push over HTTP: client side · de1a2fdd
      由 Shawn O. Pearce 提交于 
      The git-remote-curl backend detects if the remote server supports
the git-receive-pack service, and if so, runs git-send-pack in a
pipe to dump the command and pack data as a single POST request.

The advertisements from the server that were obtained during the
discovery are passed into git-send-pack before the POST request
starts.  This permits git-send-pack to operate largely unmodified.

For smaller packs (those under 1 MiB) a HTTP/1.0 POST with a
Content-Length is used, permitting interaction with any server.
The 1 MiB limit is arbitrary, but is sufficent to fit most deltas
created by human authors against text sources with the occasional
small binary file (e.g. few KiB icon image).  The configuration
option http.postBuffer can be used to increase (or shink) this
buffer if the default is not sufficient.

For larger packs which cannot be spooled entirely into the helper's
memory space (due to http.postBuffer being too small), the POST
request requires HTTP/1.1 and sets "Transfer-Encoding: chunked".
This permits the client to upload an unknown amount of data in one
HTTP transaction without needing to pregenerate the entire pack
file locally.
Signed-off-by: NShawn O. Pearce <spearce@spearce.org>
CC: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      de1a2fdd
  21. 25 10月, 2009 1 次提交
  23. 22 10月, 2009 1 次提交
  25. 20 10月, 2009 1 次提交
    • J
      Introduce commit notes · a97a7468
      由 Johannes Schindelin 提交于 
      Commit notes are blobs which are shown together with the commit
message.  These blobs are taken from the notes ref, which you can
configure by the config variable core.notesRef, which in turn can
be overridden by the environment variable GIT_NOTES_REF.

The notes ref is a branch which contains "files" whose names are
the names of the corresponding commits (i.e. the SHA-1).

The rationale for putting this information into a ref is this: we
want to be able to fetch and possibly union-merge the notes,
maybe even look at the date when a note was introduced, and we
want to store them efficiently together with the other objects.

This patch has been improved by the following contributions:
- Thomas Rast: fix core.notesRef documentation
- Tor Arne Vestbø: fix printing of multi-line notes
- Alex Riesen: Using char array instead of char pointer costs less BSS
- Johan Herland: Plug leak when msg is good, but msglen or type causes return
Signed-off-by: NJohannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: NThomas Rast <trast@student.ethz.ch>
Signed-off-by: NTor Arne Vestbø <tavestbo@trolltech.com>
Signed-off-by: NJohan Herland <johan@herland.net>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>

get_commit_notes(): Plug memory leak when 'if' triggers, but not because of read_sha1_file() failure
      a97a7468
  27. 10 10月, 2009 1 次提交
  29. 12 9月, 2009 2 次提交
  31. 08 9月, 2009 1 次提交
  33. 06 9月, 2009 1 次提交
    • J
      core.whitespace: split trailing-space into blank-at-{eol,eof} · aeb84b05
      由 Junio C Hamano 提交于 
      People who configured trailing-space depended on it to catch both extra
white space at the end of line, and extra blank lines at the end of file.
Earlier attempt to introduce only blank-at-eof gave them an escape hatch
to keep the old behaviour, but it is a regression until they explicitly
specify the new error class.

This introduces a blank-at-eol that only catches extra white space at the
end of line, and makes the traditional trailing-space a convenient synonym
to catch both blank-at-eol and blank-at-eof.  This way, people who used
trailing-space continue to catch both classes of errors.
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      aeb84b05
  35. 05 9月, 2009 1 次提交
    • J
      apply --whitespace=warn/error: diagnose blank at EOF · 77b15bbd
      由 Junio C Hamano 提交于 
      "git apply" strips new blank lines at EOF under --whitespace=fix option,
but neigher --whitespace=warn nor --whitespace=error paid any attention to
these errors.

Introduce a new whitespace error class, blank-at-eof, to make the
whitespace error handling more consistent.

The patch adds a new "linenr" field to the struct fragment in order to
record which line the hunk started in the input file, but this is needed
solely for reporting purposes.  The detection of this class of whitespace
errors cannot be done while parsing a patch like we do for all the other
classes of whitespace errors.  It instead has to wait until we find where
to apply the hunk, but at that point, we do not have an access to the
original line number in the input file anymore, hence the new field.

Depending on your point of view, this may be a bugfix that makes warn and
error in line with fix.  Or you could call it a new feature.  The line
between them is somewhat fuzzy in this case.

Strictly speaking, triggering more errors than before is a change in
behaviour that is not backward compatible, even though the reason for the
change is because the code was not checking for an error that it should
have.  People who do not want added blank lines at EOF to trigger an error
can disable the new error class.
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      77b15bbd
  37. 13 8月, 2009 1 次提交
  39. 06 8月, 2009 2 次提交
  41. 29 7月, 2009 1 次提交
  43. 26 7月, 2009 1 次提交
  45. 23 7月, 2009 1 次提交
  47. 09 7月, 2009 1 次提交
  49. 19 6月, 2009 1 次提交
    • M
      http.c: add http.sslCertPasswordProtected option · 754ae192
      由 Mark Lodato 提交于 
      Add a configuration option, http.sslCertPasswordProtected, and associated
environment variable, GIT_SSL_CERT_PASSWORD_PROTECTED, to enable SSL client
certificate password prompt from within git.  If this option is false and
if the environment variable does not exist, git falls back to OpenSSL's
prompts (as in earlier versions of git).

The environment variable may only be used to enable, not to disable
git's password prompt.  This behavior mimics GIT_NO_VERIFY; the mere
existence of the variable is all that is checked.
Signed-off-by: NMark Lodato <lodatom@gmail.com>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      754ae192
  51. 10 6月, 2009 1 次提交
  53. 01 6月, 2009 1 次提交
  55. 30 4月, 2009 1 次提交
  57. 26 4月, 2009 1 次提交
  59. 24 4月, 2009 3 次提交
  61. 23 4月, 2009 3 次提交
  63. 19 4月, 2009 1 次提交
  65. 18 4月, 2009 1 次提交