On 30/07/16 11:40, Samuli Seppänen wrote:
> Il 29/07/2016 21:13, Jonathan K. Bullard ha scritto:
>> Yesterday Lars Ingebrigtsen, who established and has run Gmane since
>> 2002, posted an article saying that Gmane might go away [1].
>>
>> He posted an update [2] which says the Gmane archive *has* gone away
>> and unless someone steps up to take it over, it is gone for good.
>>
>> The OpenVPN mailing list archives are still available on SourceForge,
>> but it might be worth thinking about adding openvpn-dev and
>> openvpn-users to The Mail Archive [3] or some other such service.
>>
>> [1] https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane
>> [2] 
>> https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/comment-page-1/#comment-13502
>> [3] https://www.mail-archive.com
>>
> 
> I looked at the mail-archive FAQ and that seemed promising. I'll take a 
> closer look in a couple of weeks.
> 
> Based on comments in the second link there's a real chance that nobody 
> will reimplement a Web UI for Gmane for hosting the archive data, and 
> that links to Gmane will be gone forever.

On LWN there are some more comments to these sad news.  I understand
Lars' motivation to step down, and I hope someone will manage to pick up
after Lars.  The reason is that gmane is mailing list archive I've found
which has a sane thread view (which also responded to keytboard events).

Jon Corbet says in a comment:

    I've been talking a bit with Lars; money doesn't seem to be the
    issue. He's really just ready to hand it off. I think we might have
    found a good prospective home for gmane, but it will take a little
    while to know for sure.

And I see that cloudflare has been put in front of gmane.org now (though
not yet working).  So these might be some traces of that.

Anyhow, this scenario is why we put Message-ID in our commit logs.  The
URL to gmane.org was primarily for convenience, the Message-ID field is
the mandatory field in our commit messages.  So unless gmane.org
re-appears or something better comes up, we will just update our git
scripts to use a different convenience URL.


-- 
kind regards,

David Sommerseth

Reply via email to