From: CityK <cityk@rogers.com>
To: Linux-media <linux-media@vger.kernel.org>,
Hlangos <henrik-linuxtv@prak.org>
Subject: Re: [linux-dvb] Linuxtv wiki needs email notification/more email-ready users
Date: Tue, 13 Oct 2009 00:52:08 -0400 [thread overview]
Message-ID: <4AD40778.6080009@rogers.com> (raw)
In-Reply-To: <4AB47066.105@rogers.com>
Hi Henrik,
CityK wrote:
> H. Langos wrote:
>
>> ...I'd like to keep an eye on changes. Not because of fear of
>> vandalisim but because changes to the templates/date potentially have
>> effects on a lot of pages.
>>
>> There are some people who day by day put a lot of effort and work into the
>> wiki and I'd like to thank them all for their continuing effort. I myself
>> have only occasionaly time to update information there and I miss a lot
>> of changes, even to the pages I watch, because the "watchlist" and "recent
>> cahnges" reaches only seven days back. Manually going through the pages on
>> my watchlist (currently 57) is not what I'd call good use of resources.
>>
>> It would be great if it was possible to get (immediate/daily/weekly?) change
>> notifications by email in order not to lose track of what is happening to
>> the pages that I care about. (I bet this is standard functionality of
>> mediawiki or at least one of the more common extentions.)
>>
In searching for something else, I came across this recent thread on the
mediawiki m/l:
http://lists.wikimedia.org/pipermail/mediawiki-l/2009-October/032214.html
There are a few suggestions in it (I just skimmed through). Perhaps one
of them would be good to implement.
next prev parent reply other threads:[~2009-10-13 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 8:09 [linux-dvb] Linuxtv wiki needs email notification/more email-ready users H. Langos
2009-09-19 5:47 ` CityK
2009-10-13 4:52 ` CityK [this message]
2009-10-14 8:53 ` H. Langos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AD40778.6080009@rogers.com \
--to=cityk@rogers.com \
--cc=henrik-linuxtv@prak.org \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox