Maggi Federico schreef:
Hello,
thanks for your quick contribution. By the way, I was browsing around
the repository and, beside its hugeness, I couldn't really find the
classic /branches /trunk /tags structure.
Am I pointing my client to the wrong repo?
The /branches, /trunk and
Ilmari Karonen schreef:
Also, note that all this is true for the main UI code. The API code
(found in api.php and under includes/api) and the AJAX code
(includes/Ajax*.php) may do things somewhat differently.
The API just uses $wgRequest through a wrapper
(ApiMain::getRequestParams()).
Hello List,
I know MW a little bit but not so well to avoid asking for hints here.
For research purposes, I am surveying code repositories of the top 10
web applications using a modified version of StatSVN.
Basically, I need to track source changes, over releases, in terms of
Lines
Maggi Federico wrote:
Hello List,
I know MW a little bit but not so well to avoid asking for hints here.
For research purposes, I am surveying code repositories of the top 10
web applications using a modified version of StatSVN.
Basically, I need to track source changes, over
Hello,
thanks for your quick contribution. By the way, I was browsing around
the repository and, beside its hugeness, I couldn't really find the
classic /branches /trunk /tags structure.
Am I pointing my client to the wrong repo?
On Mar 16, 2009, at 3:53 PM, Platonides wrote:
Maggi Federico wrote:
The functions/lines I am interested in are those somehow involved in
handling HTTP request/session/response parameters. Of course, I allow
a certain roughness in the analysis.
I am trying to build a list of such functions/lines. What would you
suggest to
Maggi Federico wrote:
Hello,
thanks for your quick contribution. By the way, I was browsing around
the repository and, beside its hugeness, I couldn't really find the
classic /branches /trunk /tags structure.
Have you read http://www.mediawiki.org/wiki/Manual:Download_from_SVN ?
