Fix broken Gmane URLs

Author: cyounkins

SoC-2014-Ideas.md

@@ -250,7 +250,7 @@ by allowing the commands to take options.  Maybe
   ```
 
 See [this
-discussion](http://thread.gmane.org/gmane.comp.version-control.git/242701)
+discussion](https://public-inbox.org/git/530DA00E.4090402%40alum.mit.edu/)
 on the mailing list for more related ideas.
 
 The goal of this project would be (1) to add the infrastructure for
@@ -298,9 +298,9 @@ to invalidate the cache correctly in the case that the configuration
 is changed while `git` is executing.
 
 See [this mailing list
-thread](http://article.gmane.org/gmane.comp.version-control.git/242952)
+thread](https://public-inbox.org/git/53108650.2020708%40alum.mit.edu/)
 and [this
-email](http://article.gmane.org/gmane.comp.version-control.git/243542)
+email](https://public-inbox.org/git/20140306194654.GA28203%40sigill.intra.peff.net/)
 for some discussion about this and related ideas.
 
  - Language: C

SoC-2014-Microprojects.md

@@ -21,7 +21,7 @@ projects](https://github.com/libgit2/libgit2/blob/development/PROJECTS.md)
 rather than the list below.*
 
 Consider [a sample email
-thread](http://thread.gmane.org/gmane.comp.version-control.git/239068),
+thread](https://public-inbox.org/git/1386590745-4412-1-git-send-email-t.gummerer%40gmail.com/),
 which shows how a developer proposed a change and a patch to implement
 it.  The problem being solved, the design of the proposed solution,
 and the implementation of that design were all reviewed and discussed,

SoC-2015-Ideas.md

@@ -48,7 +48,7 @@ proposals for other ideas related to Git or libgit2.
 ### Tighten configuration and hook execution based on the file ownership.
 
 In addition to what we discussed, I think files named by include.path
-should be honored without checking the ownership.  Cf. <http://article.gmane.org/gmane.comp.version-control.git/243628>
+should be honored without checking the ownership.  Cf. <https://public-inbox.org/git/20140307210403.GA6790%40sigill.intra.peff.net/>
 
 ### "git apply --fix-mta-corruption".
 
@@ -67,7 +67,7 @@ When your project is strictly "new features are merged into trunk,
 never the other way around", it is handy to be able to first find
 a merge on the trunk that merged a topic to point fingers at when
 a bug appears, instead of having to drill down to the individual
-commit on the faulty side branch. Cf.  <http://thread.gmane.org/gmane.comp.version-control.git/264661/focus=264720>
+commit on the faulty side branch. Cf.  <https://public-inbox.org/git/CAMo-WNYNeShbbhNfG455o7krGfY7_9zVU3dMpJ7b4Smh_AiATg%40mail.gmail.com/>
 
 #### "git bisect fixed/unfixed"
 
@@ -83,27 +83,27 @@ than defining "fixed"/"unfixed" as aliases for "bad"/"good".
 
 A patch for this feature was sent to the mailing list in this thread a
 few years ago by Dscho:
-<http://thread.gmane.org/gmane.comp.version-control.git/86063>
+<https://public-inbox.org/git/alpine.DEB.1.00.0806241515460.9925%40racer/>
 
 Unfortunately there were some problems with the patch and no one tried
 to fix them. So the same problem/suggestion is often reported on the
 mailing list, for example:
 
- - <http://thread.gmane.org/gmane.comp.version-control.git/165141>
- - <http://thread.gmane.org/gmane.comp.version-control.git/170113>
- - <http://thread.gmane.org/gmane.comp.version-control.git/182398>
+ - <https://public-inbox.org/git/855249CA-A006-475C-8F96-EFD614795064%40gmail.com/>
+ - <https://public-inbox.org/git/AANLkTinQ0rCw2ydisHra779r6_iSOxqRwOStpJrNbx7h%40mail.gmail.com/>
+ - <https://public-inbox.org/git/20110929142027.GA4936%40zelva.suse.cz/>
 
 A patch series to let "old/new" be used instead of "good/bad" was
 started here:
 
-<http://thread.gmane.org/gmane.comp.version-control.git/199758/focus=199869>
+<https://public-inbox.org/git/1339466625-17461-1-git-send-email-Valentin.Duperray%40ensimag.imag.fr/>
 
 There is still work to be done to complete it.
 
 Note than another feature with the name "git bisect fix" was suggested
 to do something else:
 
-<http://thread.gmane.org/gmane.comp.version-control.git/169026>
+<https://lore.kernel.org/lkml/200312231416.58998.kernel%40kolivas.org/>
 
 Since there have already been discussions and patches, the remaining
 work is probably less than a GSoC, so this project should be grouped
@@ -133,15 +133,15 @@ formatting, and use it consistently in the three commands.
 "git config", when removing the last variable in a section, leaves an
 empty section header behind. Anybody who wants to improve this needs
 to consider ramifications of leaving or removing comments.
-Cf. <http://article.gmane.org/gmane.comp.version-control.git/219524>
+Cf. <https://lore.kernel.org/lkml/40FFBC8B.5050407%40cox.net/>
 
 ### "git fetch --deepen"?
 
-Cf. <http://article.gmane.org/gmane.comp.version-control.git/213180> <http://article.gmane.org/gmane.comp.version-control.git/212950>
+Cf. <https://public-inbox.org/git/7vk3rkcocy.fsf%40alter.siamese.dyndns.org/> <https://public-inbox.org/git/7vobh0f5nc.fsf%40alter.siamese.dyndns.org/>
 
 ### Introduce threading to checkout codepath, possibly helping Windows folks.
 
-Cf. <http://article.gmane.org/gmane.comp.version-control.git/235874>
+Cf. <https://public-inbox.org/git/CAHOQ7J_ZZ%3D7j-5ULd7Tdvbiqg4inhwi%2Bfue_w6WAtNRkvZSwsg%40mail.gmail.com/>
 
 ### Be nicer to the user on tracked/untracked merge conflicts
 

SoC-2016-Ideas.md

@@ -113,7 +113,7 @@ should be honored without checking the ownership.  Cf. <http://article.gmane.org
 ### Implement `git apply --fix-mta-corruption`
 
 Takes eol attributes into account to correct lossage/addition of CR at
-the end of line, with updates to "am".  Cf. <http://article.gmane.org/gmane.comp.version-control.git/257445>
+the end of line, with updates to "am".  Cf. <https://public-inbox.org/git/xmqqoau6gguz.fsf%40gitster.dls.corp.google.com/>
 
 ### git bisect improvements
 
@@ -149,7 +149,7 @@ error message if 'fast' is the new term, 'slow' the old one, and if C
 is 'fast'. Instead of failing, it could offer the user to reverse the
 terms and continue the bisection.
 
-See discussion on the subject [here](http://thread.gmane.org/gmane.comp.version-control.git/272792/focus=272869).
+See discussion on the subject [here](https://public-inbox.org/git/1435337896-20709-1-git-send-email-Matthieu.Moy%40imag.fr/).
 
 The change is controversial, hence a substantial part of the project
 would be to define what is the right behavior (should it be activated
@@ -208,11 +208,11 @@ another one to give a proper GSoC project.
 "git config", when removing the last variable in a section, leaves an
 empty section header behind. Anybody who wants to improve this needs
 to consider ramifications of leaving or removing comments.
-Cf. <http://article.gmane.org/gmane.comp.version-control.git/219524>
+Cf. <https://public-inbox.org/git/20130329195155.GA19994%40sigill.intra.peff.net/>
 
 ### Introduce threading to checkout codepath, possibly helping Windows folks.
 
-Cf. <http://article.gmane.org/gmane.comp.version-control.git/235874>
+Cf. <https://public-inbox.org/git/CAHOQ7J_ZZ%3D7j-5ULd7Tdvbiqg4inhwi%2Bfue_w6WAtNRkvZSwsg%40mail.gmail.com/>
 
 ### Be nicer to the user on tracked/untracked merge conflicts
 
@@ -334,7 +334,7 @@ deep understanding of Git: how each command is meant to be used, what
 are the potential dangers, ... Reaching a solution that effectively
 protects beginners without harming anyone is much harder than it
 seems. See for example [this
-thread](http://thread.gmane.org/gmane.comp.version-control.git/285893/focus=286614)
+thread](https://public-inbox.org/git/vpqoabox66p.fsf%40anie.imag.fr/)
 for example potential objections. If chosen, this project should be
 discussed in depth on the list before and after the student
 application.

_posts/2015-03-25-edition-1.markdown

@@ -28,7 +28,7 @@ requests](https://github.com/git/git.github.io/pulls) or opening
 
 ### General
 
-* [Promoting Git developers](http://thread.gmane.org/gmane.comp.version-control.git/265165)  (*written by Junio C Hamano*)
+* [Promoting Git developers](https://public-inbox.org/git/54FDA6B5.8050505%40drmicha.warpmail.net/)  (*written by Junio C Hamano*)
 
 Following up to a message from David Kastrup, a discussion was initiated
 by Christian Couder where Michael J Gruber noted
@@ -47,7 +47,7 @@ contributors and thank for their help for each release.
 
 ### Reviews
 
-* [make git-pull a builtin](http://thread.gmane.org/gmane.comp.version-control.git/265628/)
+* [make git-pull a builtin](https://public-inbox.org/git/1426600662-32276-1-git-send-email-pyokagan%40gmail.com/)
 
 Paul Tan, who will probably apply to be a [Google Summer of Code
 (GSoC)](https://developers.google.com/open-source/soc/) student for
@@ -111,7 +111,7 @@ Regarding the test suite, Matthieu Moy suggested:
 >they do, add a failing test that passes again once you uncomment the
 >code.
 
-* [Forbid "log --graph --no-walk"](http://thread.gmane.org/gmane.comp.version-control.git/264899/)
+* [Forbid "log --graph --no-walk"](https://public-inbox.org/git/1425632110-31863-1-git-send-email-dongcan.jiang%40gmail.com/)
 
 Dongcan Jiang, who will also probably apply to be a GSoC student for
 Git this year, sent a patch to prevent `git log` from being used with both
@@ -138,7 +138,7 @@ on incoming patches:
 >
 >Okay. You might also want to cite the wider discussion[1].
 >
->[1]: http://article.gmane.org/gmane.comp.version-control.git/216083
+>[1]: https://public-inbox.org/git/7vvc9ylh97.fsf%40alter.siamese.dyndns.org/
 >
 >> revision.c: Judge whether --graph and --no-walk come together when running git-log.
 >> buildin/log.c: Set git-log cmd flag.
@@ -158,7 +158,7 @@ on the arguments it is given:
 > command about a connected history.  Otherwise, it is a command about
 > discrete point(s).
 
-* [War on broken &&-chain](http://thread.gmane.org/gmane.comp.version-control.git/265874) (*written by Junio C Hamano*)
+* [War on broken &&-chain](https://public-inbox.org/git/20150320100429.GA17354%40peff.net/) (*written by Junio C Hamano*)
 
 We often see review comments on test scripts that points out a
 breakage in the &&-chain, but what does that mean?
@@ -203,7 +203,7 @@ runs only on a case insensitive filesystem a few days later.
 
 ### Support
 
-* [Git with Lader logic](http://thread.gmane.org/gmane.comp.version-control.git/265679/)
+* [Git with Lader logic](https://public-inbox.org/git/5F9B9EBF-CD4D-42A8-8A0C-9806702231A1%40icloud.com/)
 
 People often ask the Git mailing list whether they can use Git to manage
 special content. Fortunately, the list is monitored by many experts in different
@@ -267,7 +267,7 @@ Jeff King &lt;<[email protected]>&gt;.
 > The latest maintenance release Git v2.3.2 is now available at
 > the usual places.
 
-* [Commandline GUI-tool *tig* version 2.1](http://article.gmane.org/gmane.comp.version-control.git/265298), March 11th:
+* [Commandline GUI-tool *tig* version 2.1](https://public-inbox.org/git/CAFuPQ1%2BD3QY8MxNRX87R6-nUR9eP3JRTq_yuWfRq1upQT7iC8w%40mail.gmail.com/), March 11th:
 
 > I just released version 2.1 of Tig which brings a lot of improvements to speed
 > up usage in large repositories such as the Linux kernel repo (see improvements
@@ -287,7 +287,7 @@ Jeff King &lt;<[email protected]>&gt;.
 > the usual places.  It is comprised of 26 non-merge commits since
 > v2.3.2, contributed by 11 people, 1 of which is a new contributor.
 
-* [Git v2.3.4](http://permalink.gmane.org/gmane.linux.kernel/1915412), March 23rd:
+* [Git v2.3.4](https://public-inbox.org/git/xmqqlhin8kh9.fsf%40gitster.dls.corp.google.com/), March 23rd:
 
 > The latest maintenance release Git v2.3.4 is now available at the
 > usual places.  It is comprised of 22 non-merge commits since v2.3.3,

_posts/2015-04-15-edition-2.markdown

@@ -111,7 +111,7 @@ NFS, Amazon S3 ...) and chunking for resumable downloads.
 
 ### Reviews
 
-* [Speeding up strbuf_getwholeline()](http://thread.gmane.org/gmane.comp.version-control.git/266789/focus=266796)
+* [Speeding up strbuf_getwholeline()](https://public-inbox.org/git/20150405010611.GA15901%40peff.net/)
 
 Jeff King, alias Peff, posted a patch series to address speed
 regressions when accessing the packed-refs file. This lead to
@@ -215,7 +215,7 @@ Brendan Forster put together this [Beta Testers Guide](https://gist.github.com/s
 > The following fixes have been backported to this maintenance release. [...]
 > All users of the library are encouraged to update.
 
-* [tig-2.1.1](http://article.gmane.org/gmane.comp.version-control.git/266979), April 9th
+* [tig-2.1.1](https://public-inbox.org/git/CAFuPQ1%2B5Cpb5VYPdF3E0i3Fp%2B%2BMRs6DwPnkJZ171MHNzrq5hTQ%40mail.gmail.com/), April 9th
 
 > Finally, files (or blobs) can now be searched using the new GitHub-inspired
 > [file finder](https://asciinema.org/a/18525) (press 'f' to launch it).

_posts/2015-05-13-edition-3.markdown

@@ -74,13 +74,13 @@ videos, blog posts and other materials available from her
 [gitforteams GitHub repo](https://github.com/emmajane/gitforteams), and also in an
 [upcoming Git for Teams of One or More book](http://gitforteams.com/books/).
 
-* [Git + Software Freedom Conservancy Overview](http://thread.gmane.org/gmane.comp.version-control.git/267077/)
+* [Git + Software Freedom Conservancy Overview](http://article.gmane.org/gmane.comp.version-control.git/267077)
 
 At the Contributor Summit that was part of the [Git Merge 2015](http://git-merge.com),
 Jeff King, aka Peff, gave a presentation about the status of Git as a
 [Software Freedom Conservancy (SFC)](https://sfconservancy.org/) project.
 
-Git is a [member project of the SFC since 2010](http://thread.gmane.org/gmane.comp.version-control.git/159722/).
+Git is a [member project of the SFC since 2010](https://public-inbox.org/git/20101022183027.GA12124%40sigill.intra.peff.net/).
 This gives some legal status to "The Git Project" and makes it possible for it
 to handle money (around $19,000), hold domain names (git-scm.com, git-scm.org) and
 [the "Git" trademark](https://git-scm.com/trademark), and own a Mac!
@@ -116,20 +116,20 @@ about possible changes to the current situation.
 
 ### Reviews
 
-* ["cat-file --allow-unknown-type"](http://thread.gmane.org/gmane.comp.version-control.git/268262)
+* ["cat-file --allow-unknown-type"](https://public-inbox.org/git/55463094.9040204%40gmail.com/)
 
 Karthik Nayak, a Google Summer of Code student, has been working for
 some months on developing the `--allow-unknown-type` option for `git cat-file`.
 
 He has been helped by Eric Sunshine, Ramsay Jones, Phil Hord, Charles Bailey, David Turner, Duy Nguyen,
 Jeff King and Junio Hamano, and, along the development, improving the test script led
-to a [discovery and fix of a bug](http://thread.gmane.org/gmane.comp.version-control.git/268306)
+to a [discovery and fix of a bug](https://public-inbox.org/git/1430724315-524-1-git-send-email-sunshine%40sunshineco.com/)
 in `hash-object --literally`.
 
 The 10th iteration of his patch series was merged to the 'next' branch,
 so the new option will probably appear in the next git release.
 
-* ["git help" reorganisation](http://thread.gmane.org/gmane.comp.version-control.git/268348)
+* ["git help" reorganisation](https://public-inbox.org/git/cover.1430770308.git.sebastien.guimmara%40gmail.com/)
 
 Sébastien Guimmara started working on improving the output of `git help`.
 
@@ -148,7 +148,7 @@ while.
 In the case of Sébastien's patch series, many developers helped or got
 involved in the discussions: Eric Sunshine, Junio Hamano, Stefan
 Beller, Matthieu Moy, Johannes Schindelin, Johannes Sixt. Emma Jane Hogbin Westby
-also [weighed in](http://thread.gmane.org/gmane.comp.version-control.git/268348/focus=268525)
+also [weighed in](https://public-inbox.org/git/cover.1430770308.git.sebastien.guimmara%40gmail.com//focus=268525)
 with her experience in teaching Git to people, which is a valuable
 piece of input.
 
@@ -157,7 +157,7 @@ We will see how it goes and if some improvements are merged.
 
 ### Support
 
-* [gitk won't show notes?](http://thread.gmane.org/gmane.comp.version-control.git/266662/)
+* [gitk won't show notes?](https://public-inbox.org/git/551D99B9.7040200%40ubuntu.com/)
 
 Phillip Susi had trouble getting gitk to show notes. Michael J. Gruber
 tried to help him, but it didn't work when adding a note while gitk is
@@ -175,7 +175,7 @@ Paul agreed that indeed works need to be done to fix this problem. He
 asked if `git notes list` is the best way to find out all the current
 notes, and Johan Herland who developed `git notes` answered yes.
 
-* [git ls-files wildcard behavior considered harmful](http://thread.gmane.org/gmane.comp.version-control.git/266486/)
+* [git ls-files wildcard behavior considered harmful](https://public-inbox.org/git/20150330230459.GA13927%40kitenet.net/)
 
 Joey Hess who is developing [git-annex](https://git-annex.branchable.com/) was surprised by how
 `git ls-files` expands wildcard characters like `*[]` and the fact that escaping these characters
@@ -204,16 +204,16 @@ environment variable have been created especially for this purpose and
 it is a good idea to use them in script or tools, like GitHub is doing
 on their servers.
 
-* [No longer builds with NO_IPV6?](http://thread.gmane.org/gmane.comp.version-control.git/268406)
+* [No longer builds with NO_IPV6?](https://public-inbox.org/git/CAK4aQQJ9yT8%2BQ9jPQ78cauhyPj3j5WmpgrQJ5%3DcA-ECjaWn8BQ%40mail.gmail.com/)
 
 Eduardo Espejo found that Git does not compile anymore when using the
 `NO_IPV6` configuration switch. And it is not the first time that
-[someone finds out that Git such a `NO_IPV6` breakage](http://thread.gmane.org/gmane.comp.version-control.git/28033/).
+[someone finds out that Git such a `NO_IPV6` breakage](https://public-inbox.org/git/20060928184814.GA4294%40steel.home/).
 
 This time Junio Hamano, the Git maintainer, fixed the breakage in
 "daemon.c", but more importantly found that `NO_CURL` and `NO_EXPAT`
 configurations did not to pass the test suite.
-So helped by Jeff King [he quickly fixed that too](http://thread.gmane.org/gmane.comp.version-control.git/268467/).
+So helped by Jeff King [he quickly fixed that too](https://public-inbox.org/git/xmqq6185d4o1.fsf%40gitster.dls.corp.google.com/).
 And now he has a nightly cron job to try building
 and testing a few selected configurations.
 
@@ -251,7 +251,7 @@ work on Git scalability issues. If you are interested please contact
 
 ### Event
 
-[GSoC 2015: 2 accepted proposals](http://thread.gmane.org/gmane.comp.version-control.git/267878)
+[GSoC 2015: 2 accepted proposals](https://public-inbox.org/git/vpqoam9mjuo.fsf%40anie.imag.fr/)
 
 For a long time Git has been participating in [the Google Summer of Code](http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/about_page).
 This summer two students, Paul Tan and Karthik Nayak, mentored by four experienced Git developers, Johannes Schindelin, Stefan Beller, Matthieu Moy and Christian Couder, will work on improving Git and will receive a stipend from Google.