OK, I'm pretty happy with
$ svn diff -r HEAD RELEASE-NOTES
However that gives a backwards view,
--- RELEASE-NOTES (revision 81238)
+++ RELEASE-NOTES (working copy)
I want
--- RELEASE-NOTES (working copy)
+++ RELEASE-NOTES (revision 81238)
But
$ svn help diff
is written to
2011/1/29 Amir E. Aharoni amir.ahar...@mail.huji.ac.il:
A little bug i reported to Mozilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=629878
This happens in Wikipedia and Wordpress, but not in GMail, so it may
interest MediaWiki developers.
Thanks for notifying the list. I've commented
2011/1/30 Brion Vibber br...@pobox.com:
I noticed a regression in the JS minification with a bit of sloppy
third-party code being imported through ResourceLoader in SVGEdit:
https://bugzilla.wikimedia.org/show_bug.cgi?id=27046
Fixed now. The regex stripping C++-style // comments was also
Hey,
That makes it rather clear I'm not familiar enough with the parser to
implement a wrapper class such as ParserHook. Most extension developers will
likely not know a lot more then me about it, so I think there definitely is
a need to provide some abstraction for the most common use cases,
Daniel Friesen wrote:
setHook (old style tag hooks), and setFunctionTagHook (new style function tag
hooks).
setHook and setFunctionTagHook both set tag style hooks. Originally we
just had setHook, it had one short argument list. Later on that argument
list was changed to add $frame to
jida...@jidanni.org wrote:
OK, I'm pretty happy with
$ svn diff -r HEAD RELEASE-NOTES
However that gives a backwards view,
--- RELEASE-NOTES (revision 81238)
+++ RELEASE-NOTES (working copy)
I want
--- RELEASE-NOTES (working copy)
+++ RELEASE-NOTES (revision 81238)
But
$
On 11-01-31 09:36 AM, Platonides wrote:
Daniel Friesen wrote:
setHook (old style tag hooks), and setFunctionTagHook (new style function
tag hooks).
setHook and setFunctionTagHook both settag style hooks. Originally we
just had setHook, it had one short argument list. Later on that argument
An interesting idea just popped into my head, as a combination of my
explorations through the dom preprocessor and my attempt at deferring
editsection replacement till after parsing is done so that skins can
modify the markup used in an editsection link in a skin-specific way
without breaking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've set up an NNTP gateway for Wikimedia mailing lists. The
wikimedia.* hierarchy is available via news.tcx.org.uk. More
information: http://news.tcx.org.uk/wikimedia.html.
Unlike GMane, this gateway does not rename lists (all lists are
Adding yet another discreet parsing step is the reverse of what a lot of people
hoping to clean up wikitext are heading towards.
What some of us have been kicking around would be migrating away from
pre-procesing the text at all. Instead the text should be parsed in a single
step into an
On 11-01-31 01:47 PM, River Tarnell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've set up an NNTP gateway for Wikimedia mailing lists. The
wikimedia.* hierarchy is available via news.tcx.org.uk. More
information:http://news.tcx.org.uk/wikimedia.html.
Unlike GMane, this
Usually I don't reply that much on other threads, but for this: +1.
Jan Paul
On 31-Jan-2011, at 22:55, Trevor Parscal wrote:
Adding yet another discreet parsing step is the reverse of what a lot of
people hoping to clean up wikitext are heading towards.
What some of us have been kicking
On Mon, Jan 31, 2011 at 4:55 PM, Trevor Parscal tpars...@wikimedia.org wrote:
Adding yet another discreet parsing step is the reverse of what a lot of
people hoping to clean up wikitext are heading towards.
What system do you propose that would retain the performance benefits
of this
Daniel Friesen wrote:
I think there's a little more difference between setHook and
setFunctionTagHook than you mention.
At the very least, extensionSubstitution outputs a function tag hook
directly, while putting a normal tag hook into the general strip state
and outputting a marker.
Daniel Friesen wrote:
An interesting idea just popped into my head, as a combination of my
explorations through the dom preprocessor and my attempt at deferring
editsection replacement till after parsing is done so that skins can
modify the markup used in an editsection link in a
In article 4d47370a.5030...@nadir-seen-fire.com,
Daniel Friesen li...@nadir-seen-fire.com wrote:
On 11-01-31 01:47 PM, River Tarnell wrote:
I've set up an NNTP gateway for Wikimedia mailing lists. The
wikimedia.* hierarchy is available via news.tcx.org.uk. More
On 11-01-31 03:43 PM, River Tarnell wrote:
In article4d47370a.5030...@nadir-seen-fire.com,
Daniel Friesenli...@nadir-seen-fire.com wrote:
On 11-01-31 01:47 PM, River Tarnell wrote:
I've set up an NNTP gateway for Wikimedia mailing lists. The
wikimedia.* hierarchy is available via
In article 4d47502f.1070...@nadir-seen-fire.com,
Daniel Friesen li...@nadir-seen-fire.com wrote:
On 11-01-31 03:43 PM, River Tarnell wrote:
This is a test post. If you can see it, then posting is now working (at
least somewhat).
I see it off gmane. However either it hasn't made it to the new
In article 4d47502f.1070...@nadir-seen-fire.com,
Daniel Friesen li...@nadir-seen-fire.com wrote:
On 11-01-31 03:43 PM, River Tarnell wrote:
This is a test post. If you can see it, then posting is now working (at
least somewhat).
I see it off gmane. However either it hasn't made it to the new
On 11-01-31 04:30 PM, River Tarnell wrote:
In article4d47502f.1070...@nadir-seen-fire.com,
Daniel Friesenli...@nadir-seen-fire.com wrote:
On 11-01-31 03:43 PM, River Tarnell wrote:
This is a test post. If you can see it, then posting is now working (at
least somewhat).
I see it off gmane.
Rob Lanphier wrote:
Just repeating something I just posted to
http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/
Thank you for posting here. I'm not sure about others, but I rarely visit
techblog.wikimedia.org. It's great news. :-)
The engineering team is busy working on the
Rob said
--Hi everyone,
Just repeating something I just posted to
http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/
The engineering team is busy working on the deployment of the 1.17 branch of
MediaWiki[1]. We plan to roll this out next week to all languages and
projects,
On Mon, Jan 31, 2011 at 7:41 PM, MZMcBride z...@mzmcbride.com wrote:
Rob Lanphier wrote:
Just repeating something I just posted to
http://techblog.wikimedia.org/2011/02/planned-1-17-deployment/
Thank you for posting here. I'm not sure about others, but I rarely visit
23 matches
Mail list logo
