Retirement of SVN Commitfilter and Legacy Get Hot New Stuff systems

[Boudewijn Rempt]

Nah, it isn't that important. Just subscribe to the commits mailing list
and add some rules to your email client to separate out the various 
repositories is easy enough. _If_ the commit filter were really important,
someone would have maintained it, right? If there's no maintainer, there's
no importance.

On Sun, 30 Jul 2017, Gilles Caulier wrote:

> Hi all,
> 
> Idem for me with digiKam. Commit filter is a main tool used to follow
> all contributors and see if something is badly done with commits. It's
> main rules for open source project with a large amount of code, and a
> lots of coder (as students)
> 
> Please reconsider to revival this important piece of software. It's
> very important...
> 
> Best
> 
> Gilles Caulier
> 
> 2017-07-30 13:34 GMT+02:00 Dominik Haumann <dhaumann at kde.org>:
> > Hi,
> >
> > On Sat, Jul 29, 2017 at 1:28 PM, Ben Cooksley <bcooksley at kde.org> wrote:
> >> Hi all,
> >> [...]
> >> Due to the age of the system and the limited use of the two services
> >> hosted on the system (with SVN Commitfilter having very limited
> >> application since our migration to Git) we've determined that the best
> >> course of action is to archive both services and shutdown the machine.
> >> [...]
> >
> > I am still using commit-filter to read all diffs for kate.git,
> > syntax-highlighting.git,
> > ktexteditor.git, and some dedicated authors.
> >
> > For me, commit-filter was always a very convenient way of tracking KDE
> > development, and subscribing to some git on phabricator is not good enough
> > for me (I like the current form of generated mails much more).
> >
> > Is the solution to subscribe to all kde-commits at kde.org, and then do the
> > filtering myself, or is there still another way / or any plans to get
> > commit-filter
> > back?
> >
> > Greetings
> > Dominik
> 

-- 
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org