MaintNotes: post 1.7.7.4 update
Junio C Hamano committed
Nov 18, 2011 at 14:09 UTC
081bb7fa5f4fc869de8fafd2caf3e29aa8a623f5
1 file changed
+16
-22
MaintNotes
+16
-22
@@ -52,13 +52,13 @@ on the #git IRC channel on Freenode. Its log is available at:
52
53
* Reporting bugs
54
55
-When you think git does not behave as you expect, please do not stop your
56
-bug report with just "git does not work". "I tried to do X but it did not
57
-work" is not much better, neither is "I tried to do X and git did Y, which
58
-is broken". It often is that what you expect is _not_ what other people
59
-expect, and chances are that what you expect is very different from what
60
-people who have worked on git have expected---otherwise, the behavior
61
-would have been changed to match your expectation long time ago.
55
+When you think git does not behave as you expect, please do not stop
56
+your bug report with just "git does not work". "I used git in this
57
+way, but it did not work" is not much better, neither is "I used git
58
+in this way, and X happend, which is broken". It often is that git is
59
+correct to cause X happen in such a case, and it is your expectation
60
+that is broken. People would not know what other result Y you expected
61
+to see instead of X, if you left it unsaid.
62
63
Please remember to always state
64
@@ -67,9 +67,9 @@ Please remember to always state
67
- what you did (the version of git and the command sequence to reproduce
68
the behavior);
69
70
- - what you saw happen;
70
+ - what you saw happen (X above);
71
72
- - what you expected to see; and
72
+ - what you expected to see (Y above); and
73
74
- how the last two are different.
75
@@ -78,17 +78,16 @@ hints.
78
79
* Repositories, branches and documentation.
80
81
-My public git.git repository is at:
81
+My public git.git repositories are at:
82
83
git://git.kernel.org/pub/scm/git/git.git/
84
- git://repo.or.cz/alt-git.git
85
- https://github.com/git/git
84
+ git://repo.or.cz/alt-git.git/
85
+ https://github.com/git/git/
86
https://code.google.com/p/git-core/
87
+ git://git.sourceforge.jp/gitroot/git-core/git.git/
88
+ git://git-core.git.sourceforge.net/gitroot/git-core/git-core/
89
88
-There are a few other mirrors I push into at sourceforge and github as
89
-well.
90
-
91
-Their gitweb interfaces are found at:
90
+A few gitweb interfaces are found at:
91
92
http://git.kernel.org/?p=git/git.git
93
http://repo.or.cz/w/alt-git.git
@@ -116,7 +115,7 @@ Whenever a feature release is made, "maint" branch is forked off from
115
release are applied to this branch and maintenance releases are cut from
116
it. The maintenance releases are named with four dotted decimal, named
117
after the feature release they are updates to; the last such release was
119
-1.7.7.1. New features never go to this branch. This branch is also
118
+1.7.7.4. New features never go to this branch. This branch is also
119
merged into "master" to propagate the fixes forward.
120
121
A new development does not usually happen on "master". When you send a
@@ -208,8 +207,3 @@ I have relied on and expect to continue relying on heavily:
207
- People on non-Linux platforms for keeping their eyes on portability;
208
especially, Randal Schwartz, Theodore Ts'o, Jason Riedy, Thomas Glanzmann,
209
Brandon Casey, Jeff King, Alex Riesen and countless others.
211
-
212
-* This document
213
-
214
-The latest copy of this document is found in git.git repository,
215
-on 'todo' branch, as MaintNotes.