Skip to content

G
git

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

从无法访问的项目Fork

通知 2
Star 1
Fork 0
G
git

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

切换分支/标签
  1. 13 9月, 2011 1 次提交
  3. 07 9月, 2011 1 次提交
  5. 25 8月, 2011 1 次提交
  7. 27 6月, 2011 1 次提交
  9. 24 6月, 2011 1 次提交
    • J
      git.txt: de-emphasize the implementation detail of a ref · 0abcfbff
      由 Junio C Hamano 提交于 
      It is an unimportant implementation detail that branches and tags are
stored somewhere under $GIT_DIR/refs directory, or the name of the commit
that will become the parent of the next commit is stored in $GIT_DIR/HEAD.

What is more important is that branches live in refs/heads and tags live
in refs/tags hierarchy in the ref namespace, and HEAD means the tip of the
current branch.
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      0abcfbff
  11. 02 6月, 2011 1 次提交
  13. 27 5月, 2011 1 次提交
  15. 20 5月, 2011 1 次提交
  17. 05 5月, 2011 1 次提交
  19. 02 5月, 2011 2 次提交
  21. 24 4月, 2011 1 次提交
  23. 20 4月, 2011 1 次提交
  25. 15 4月, 2011 1 次提交
  27. 07 4月, 2011 1 次提交
  29. 03 4月, 2011 1 次提交
  31. 13 3月, 2011 1 次提交
    • J
      docs: point git.txt author credits to git-scm.com · d8f708f8
      由 Jeff King 提交于 
      There is a nice shortlog-ish output of the authors there. We
also point people directly to shortlog, but of course they
might be reading the documentation online or from a binary
package of git.
      d8f708f8
  33. 11 3月, 2011 1 次提交
    • J
      doc: drop author/documentation sections from most pages · 48bb914e
      由 Jeff King 提交于 
      The point of these sections is generally to:

  1. Give credit where it is due.

  2. Give the reader an idea of where to ask questions or
     file bug reports.

But they don't do a good job of either case. For (1), they
are out of date and incomplete. A much more accurate answer
can be gotten through shortlog or blame.  For (2), the
correct contact point is generally git@vger, and even if you
wanted to cc the contact point, the out-of-date and
incomplete fields mean you're likely sending to somebody
useless.

So let's drop the fields entirely from all manpages except
git(1) itself. We already point people to the mailing list
for bug reports there, and we can update the Authors section
to give credit to the major contributors and point to
shortlog and blame for more information.

Each page has a "This is part of git" footer, so people can
follow that to the main git manpage.
      48bb914e
  35. 12 2月, 2011 1 次提交
  37. 31 1月, 2011 1 次提交
  39. 25 1月, 2011 1 次提交
  41. 06 1月, 2011 1 次提交
  43. 23 12月, 2010 1 次提交
  45. 17 12月, 2010 1 次提交
  47. 10 12月, 2010 1 次提交
  49. 22 10月, 2010 1 次提交
  51. 14 10月, 2010 1 次提交
  53. 09 10月, 2010 1 次提交
  55. 30 9月, 2010 1 次提交
  57. 19 9月, 2010 1 次提交
  59. 07 9月, 2010 1 次提交
  61. 04 9月, 2010 1 次提交
  63. 01 9月, 2010 1 次提交
  65. 20 8月, 2010 1 次提交
  67. 03 8月, 2010 1 次提交
  69. 28 7月, 2010 3 次提交
  71. 22 7月, 2010 1 次提交
  73. 06 7月, 2010 1 次提交