Skip to content

Commit a37a17b

Browse files
committed
MaintNotes: http://gmane is no longer with us
Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent 8800e19 commit a37a17b

File tree

1 file changed

+17
-9
lines changed

1 file changed

+17
-9
lines changed

MaintNotes

Lines changed: 17 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -30,21 +30,29 @@ becomes calmer before sending such a reminder.
3030

3131
The list archive is available at a few public sites:
3232

33-
http://news.gmane.org/gmane.comp.version-control.git/
33+
http://public-inbox.org/git/
3434
http://marc.info/?l=git
3535
http://www.spinics.net/lists/git/
3636

3737
For those who prefer to read it over NNTP:
3838

39-
nntp://news.gmane.org/gmane.comp.version-control.git
39+
nntp://news.gmane.org/gmane.comp.version-control.git
4040

41-
When you point at a message in a mailing list archive, using
42-
gmane is often the easiest to follow by readers, like this:
41+
is still available. An alternative
4342

44-
http://thread.gmane.org/gmane.comp.version-control.git/27/focus=217
43+
nntp://news.public-inbox.org/inbox.comp.version-control.git
4544

46-
as it also allows people who subscribe to the mailing list as gmane
47-
newsgroup to "jump to" the article.
45+
will become usable once it catches up with old messages.
46+
47+
When you point at a message in a mailing list archive, using its
48+
message ID is often the most robust (if not very friendly) way to do
49+
so, like this:
50+
51+
http://public-inbox.org/git/Pine.LNX.4.58.0504150753440.7211@ppc970.osdl.org
52+
53+
Often these web interfaces accept the message ID with enclosing <>
54+
stripped (like the above example to point at one of the most important
55+
message in the Git list).
4856

4957
Some members of the development community can sometimes be found on
5058
the #git and #git-devel IRC channels on Freenode. Their logs are
@@ -156,8 +164,8 @@ of last-minute issues. The maintenance releases used to be named with
156164
four dotted decimal, named after the feature release they are updates
157165
to (e.g. "1.8.5.1" was the first maintenance release for "1.8.5"
158166
feature release). These days, maintenance releases are named by
159-
incrementing the last digit of three-dotted decimal name (e.g. "2.8.3"
160-
is the third maintenance release for the "2.8" series).
167+
incrementing the last digit of three-dotted decimal name (e.g. "2.9.3"
168+
is the third maintenance release for the "2.9" series).
161169

162170
New features never go to the 'maint' branch. This branch is also
163171
merged into "master" to propagate the fixes forward as needed.

0 commit comments

Comments
 (0)