| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Closes #5541.
|
|
|
|
|
|
|
|
|
|
His homepage is no longer online.
|
|
The official badge cannot be used because it is red, which is commonly
used in badges to indicate failure. Also, for this package, the
official badge does not actually exist at the expected url.
|
|
|
|
- Remove joke badges to make room for more serious badges.
- Remove GPLv3 badge because that information is already
being displayed prominently in several other places.
|
|
|
|
|
|
|
|
https://help.twitter.com/en/rules-and-policies/social-platforms-policy
> Twitter is where the public conversation is happening, and where
> people from all over the globe come to promote their businesses,
> art, ideas, and more. We know that many of our users may be active
> on other social media platforms; however, going forward, Twitter
> will no longer allow free promotion of specific social media
> platforms on Twitter.
Fair enough. I no longer provide free promotion for Twitter either.
|
|
|
|
|
|
|
|
|
|
Favor links over duplicating information and then letting it get
out-of-date. Of course links may break too, so fix those too.
|
|
|
|
|
|
npostavs/emacs-travis is replaced with the purcell/setup-emacs action.
The host operating system version is bumped from Ubuntu Xenial (16.04)
to Bionic (20.04), as 16.04's curl doesn't have --retry-connrefused,
which is needed by purcell/setup-emacs.
Notification settings are configured per-user in their GitHub settings:
https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options
|
|
|
|
|
|
|
|
... while remove some other options, which I no longer prefer.
|
|
|
|
|
|
|
|
|
|
This reverts commit 884116790e7700cc879e950610afb73123608de4.
|
|
Fixes #3565.
|
|
|
|
|
|
|
|
|
|
|
|
I am considering it a failed experiment. The hope was that Magit
users would stick around help each other. But very few people beside
maintainers of Magit and related packages actually do help other users
more than once or twice. Most users leave once they got their own
question answered.
I don't find it a rewarding experience to help users in the Gitter
chat. Users who ask for help there tend to do less research on their
own than those who ask questions on the Emacs Stackexchange site.
That is one reason why I prefer the latter, it actively encourages
those in need to do their part. Another major benefit is that by
helping someone there, one potentially helps many users. Unlike the
Gitter chats, the QA sites are searchable and provide lasting value.
Therefore I am removing all the links to the Gitter chat and will
visit it less often, but I will keep it open, for the time being at
least.
|
|
|
|
All the cool kids have them now, again.
|
|
|
|
|
|
Thank you again!
|
|
I still accept donations there but I do not want to advertise it and
while I won't do so for the time being it is quite possible that I
will eventually encourage users to move their donations away from this
abysmal service.
The owners take a 10% share (on top of the processing fees), while the
work is being done by overworked volunteers. Support requests are not
being answered, unless it happens in public (on Twitter). Payouts
aren't performed by the end of the week as promised but take a month
or more. It has been suggest that at least the documentation should
be adjusted accordingly, but nothing has happened. Once your login
has timed out it is not possible to login again (or doing so would at
least require some research on the users part) and the underlying
issues have been reported three months ago.
Did I mention you pay 10% for this?
|
|
Which is sad, it was the most friendly, cheap and reliable of the
available alternatives.
|
|
|
|
|
|
|
|
|
|
This reverts commit aeee52f2675963ce274231cf7b0f9c771bd2d7aa.
|
