12:00:34 RRSAgent has joined #hg-talk 12:00:34 logging to http://www.w3.org/2007/03/22-hg-talk-irc 12:00:37 zakim, this will be project 12:00:37 I do not see a conference matching that name scheduled within the next hour, tlr 12:30:34 zakim, this will be globa 12:30:34 ok, tlr; I see Team_Global(review)8:00AM scheduled to start 30 minutes ago 12:53:27 Team_Global(review)8:00AM has been moved to #hg by RalphS 12:55:26 s-mon has joined #hg-talk 12:55:58 DanC has joined #hg-talk 12:58:56 agenda + Convene, take roll 12:59:06 agenda + Meeting record visibility 12:59:22 agenda + The Mercurial SCM, presentation by Matt Mackall http://www.selenic.com/mercurial/w3c-talk/ 12:59:30 RalphS has joined #hg-talk 12:59:31 agenda + Fractal project organization 12:59:40 agenda + hg hosting, large projects 13:00:03 Yves has joined #hg-talk 13:00:03 zakim, conf? 13:00:03 I don't understand your question, RalphS. 13:00:06 zakim, what conf? 13:00:06 I don't understand your question, RalphS. 13:00:09 zakim, what conference? 13:00:09 I don't understand your question, RalphS. 13:00:11 zakim, what conference is this? 13:00:11 no conference has been selected, RalphS 13:00:12 mpm has joined #hg-talk 13:00:16 zakim, move review to here 13:00:17 ok, RalphS; that matches Team_Global(review)8:00AM 13:00:22 zakim, who's on the phone? 13:00:22 On the phone I see MIT531, Kazuyuki (muted) 13:00:37 DanC has changed the topic to: The Mercurial SCM http://www.selenic.com/mercurial/w3c-talk/ 13:00:38 ivan has joined #hg-talk 13:00:40 olivier has joined #hg-talk 13:00:50 +Simon 13:00:58 +DanC 13:01:04 + +1.415.200.aaaa 13:01:33 Zakim, aaaa is mpm 13:01:33 +mpm; got it 13:01:47 +Yves 13:01:55 Zakim, take up item 1 13:01:55 agendum 1. "Convene, take roll" taken up [from DanC] 13:02:04 Zakim, who's on the phone? 13:02:04 On the phone I see MIT531, Kazuyuki (muted), Simon, DanC, mpm, Yves 13:02:12 caribou has joined #hg-talk 13:02:25 fsasaki has joined #hg-talk 13:02:45 +??P3 13:02:51 zakim, who's in mit531? 13:02:51 MIT531 has only MIT531 13:02:52 zakim, ??P3 is me 13:02:53 +olivier; got it 13:02:57 zakim, mit531 has Steve, Philippe, Ralph 13:02:57 +Steve, Philippe, Ralph; got it 13:03:03 gerald has joined #hg-talk 13:03:09 karl has joined #hg-talk 13:03:42 dom has joined #hg-talk 13:03:46 + +33.4.94.06.aabb 13:03:47 +??P5 13:03:47 Steven has joined #hg-talk 13:03:51 Zakim, aabb is me 13:03:51 +dom; got it 13:03:54 zakim, ??P5 is m 13:03:54 +m; got it 13:03:57 zakim, dial steven-617 13:03:57 ok, Steven; the call is being made 13:03:59 +Steven 13:04:03 -dom 13:04:06 zakim, mute me 13:04:06 Steven should now be muted 13:04:16 rigo has joined #hg-talk 13:04:17 zakim, m is ivan 13:04:17 sorry, ivan, I do not recognize a party named 'm' 13:04:19 +Gerald 13:04:27 zakim, who is here? 13:04:27 On the phone I see MIT531, Kazuyuki (muted), Simon, DanC, mpm, Yves, olivier (muted), m, Steven (muted), Gerald (muted) 13:04:29 MIT531 has Steve, Philippe, Ralph 13:04:30 On IRC I see rigo, Steven, dom, karl, gerald, fsasaki, caribou, olivier, ivan, mpm, Yves, RalphS, DanC, s-mon, RRSAgent, Zakim, tlr 13:04:39 zakim, m is ivan 13:04:39 sorry, Steven, I do not recognize a party named 'm' 13:04:40 +dom 13:04:43 Zakim, mute me 13:04:43 dom should now be muted 13:05:03 steve has joined #hg-talk 13:05:19 +Felix 13:06:05 ack me 13:06:11 zakim, mit531 also has TimBL 13:06:11 +TimBL; got it 13:06:18 zakim, list participants 13:06:18 As of this point the attendees have been Kazuyuki, Simon, DanC, +1.415.200.aaaa, mpm, Yves, olivier, Steve, Philippe, Ralph, +33.4.94.06.aabb, dom, m, Steven, Gerald, Felix, TimBL 13:06:19 Zakim, mute me 13:06:21 dom should now be muted 13:06:31 kaz has joined #hg-talk 13:06:35 plh has joined #hg-talk 13:06:51 zakim, produce a map of where people are please 13:06:51 I don't understand 'produce a map of where people are', RalphS 13:07:09 Zakim, pick a scribe 13:07:09 Not knowing who is chairing or who scribed recently, I propose Yves 13:07:21 timbl has joined #hg-talk 13:07:36 Zakim, pick a scribe 13:07:36 Not knowing who is chairing or who scribed recently, I propose Kazuyuki (muted) 13:07:55 Zakim, pick a scribe 13:07:55 Not knowing who is chairing or who scribed recently, I propose Steve 13:08:01 zakim, unmute me 13:08:01 Kazuyuki should no longer be muted 13:08:13 Zakim, pick a scribe 13:08:13 Not knowing who is chairing or who scribed recently, I propose Ralph 13:08:18 sigh 13:08:27 dern you, zakim :) 13:08:29 Scribe: Ralph 13:08:37 absence shows the following out of the office: 13:08:37 Daniel D., Danny W., Fumihiro, Ian J., Jose M., Judy, 13:08:37 Mimasa, Michael C., Philipp H., Shadi, Shawn 13:08:46 s/sigh/oh yes, I want to scribe!/ 13:08:46 Zakim, next item 13:08:46 agendum 2. "Meeting record visibility" taken up [from DanC] 13:08:53 ted has joined #hg-talk 13:08:56 jose has joined #hg-talk 13:08:56 +Ted 13:09:31 +Thomas 13:09:32 RESOLVED: world-visible records 13:09:38 rrsagent, please make record public 13:09:41 ericP has joined #hg-talk 13:09:44 Zakim, next item 13:09:44 agendum 2 was just opened, DanC 13:09:48 Zakim, close item 2 13:09:48 agendum 2, Meeting record visibility, closed 13:09:50 Zakim, next item 13:09:50 I see 3 items remaining on the agenda; the next one is 13:09:51 3. The Mercurial SCM, presentation by Matt Mackall http://www.selenic.com/mercurial/w3c-talk/ [from DanC] 13:09:53 agendum 3. "The Mercurial SCM, presentation by Matt Mackall http://www.selenic.com/mercurial/w3c-talk/" taken up [from DanC] 13:09:53 TimBL: Creative Commons Attribution Non-Commercial :) 13:10:17 zakim, dial jose-617 13:10:17 ok, jose; the call is being made 13:10:19 +Jose 13:10:22 zakim, mute me 13:10:22 Jose should now be muted 13:11:12 TimBL notes slides don't seem to work with safari. remote/slidey issue? 13:11:16 +??P2 13:11:23 Zakim, ??P2 is me 13:11:23 +ericP; got it 13:11:33 ht has joined #hg-talk 13:11:40 zakim, please call ht-781 13:11:40 ok, ht; the call is being made 13:11:42 +Ht 13:11:44 Zakim, remind us in 30 minutes to check the time 13:11:44 ok, DanC 13:11:44 Presenter: Matt Mackall, Selenic 13:12:03 Slide 1: Title http://www.selenic.com/mercurial/w3c-talk/#(1) 13:12:35 slide 2 "Why a New SCM?" http://www.selenic.com/mercurial/w3c-talk/#(2) 13:14:03 q+ to ask for a use case for a repeated merge 13:14:17 (i have a sense that that's a major motivator here) 13:15:21 ack ericp 13:15:21 ericP, you wanted to ask for a use case for a repeated merge 13:15:22 Matt: "your tea is still warm" came from someone at Sun, noticing merges were faster 13:15:51 ... given two lines of history; stable branch and unstable branch 13:16:03 ... bug fixes often committed to 'stable' but you want them also in 'unstable' 13:16:20 ... each time you pull patches across to 'unstable' you want to remember what happened the last time you merged 13:16:30 EricP: like cvs -j ? 13:16:43 Matt: right. cvs and svn do not remember the previous merge point 13:16:52 http://www.w3.org/Talks/Tools/Slidy/slidy.js Line 146: Can't hanlde non-ascii in string: "flèches" 13:16:53 ... so you have to revisit all the same conflicts again 13:17:44 slide 3: "Why a decentralized system?" http://www.selenic.com/mercurial/w3c-talk/#(3) 13:18:50 -Gerald 13:19:01 agenda+ The toplogy of update flows in a large development system with overlapping cokmmunities with diff't access rights. Wrt slide 3 13:19:16 offline work++ 13:19:18 Matt: centralized systems are burdensome for people who work without write access as they have larger merges to deal with, thus slow 13:19:55 Liam has joined #hg-talk 13:20:10 ... consider folks like freebsd developers; a few people have write access to the repository, a large number of people have to go through those few for commits 13:20:36 ... so benefits of version control are not available to many 13:20:54 ... better to have ability to do local commits 13:21:04 ... permit off-line commits 13:21:13 ... sync whenever you feel you need to do so 13:21:31 -> http://www.selenic.com/mercurial/w3c-talk/#(4) The Mercurial basics 13:21:49 Matt: every hg repository is a working directory ala cvs plus a private store 13:22:03 ... explicit checkout not required 13:22:11 ... store has complete private copy of entire project history 13:22:30 ... no need to communicate with original server to do work on the project 13:22:50 ... the copy you have is equivalent to what you got from the original server; it has full revision information 13:23:04 q+ to ask Is the store append-only? Optimised for getting latest version? 13:23:13 -> http://www.selenic.com/mercurial/w3c-talk/#(5) Making a commit 13:23:31 (the first time I used hg on a plane, it felt really revolutionary. http://dig.csail.mit.edu/breadcrumbs/node/96 ) 13:23:34 ack timbl 13:23:34 timbl, you wanted to ask Is the store append-only? Optimised for getting latest version? 13:23:45 Tim: does the store keep the history as append-only? 13:23:59 q+ to check about the nature of revs. . . 13:24:07 ... for what is it optimized? latest version or fetching full history? 13:24:21 Matt: append-only. small delta tacked on to end of file for revision n+1 13:24:25 ... uses 13:24:32 ... uses 'revlog' format that I invented 13:24:48 ... rougly like format of MPEG file 13:24:59 ... small deltas and periodic full images 13:25:08 ... you can seek directly in and read a small chunk 13:25:12 -> http://www.selenic.com/mercurial/wiki/index.cgi/Design revlog design note 13:25:23 ... the amount of data you have to read is equivalent to the uncompressed size of the content 13:25:32 ... so both append-only and very fast 13:25:55 ... for files with very long history the index is separate and also append-only 13:26:14 ... for files with historys < 128k, the index is combined in the same file and read with one i/o 13:26:16 q? 13:26:20 ack ht 13:26:20 ht, you wanted to check about the nature of revs. . . 13:26:44 Henry: in cvs, every file has its own revision history 13:26:57 ... if you've chosen to branch you name the files in that branch 13:27:14 ... whereas in svn the world has a revision history and every change is considered a change to the world 13:27:18 (this is agendum 4, btw) 13:27:25 ... have I framed this correctly? which is hg? 13:27:34 Matt: hg makes atomic project-wide snapshots 13:27:46 ... revlog for each file plus a "manifest" 13:27:55 ... manifest is a list of all files in a project for a given changeset 13:28:06 ... recursive pointers into manifest 13:28:18 ... so hg is in the latter camp; a project-wide sense of the state of each file 13:28:33 agenda? 13:28:37 rrsagent, please make record public 13:29:02 -> http://www.selenic.com/mercurial/w3c-talk/#(6) Revisions, Changesets, Heads, and Tip 13:29:25 I wonder whether projects can be nested.... concerned about 'project-wide" scalability... I giess that is agendum #4 13:29:56 recursive hash, like rsync? 13:30:28 Bert has joined #hg-talk 13:31:17 +Bert 13:31:24 [I suppose, then, that the act of starting a new project is "collecting tips" :) ] 13:31:32 Agenda: http://www.w3.org/mid/1174447602.32136.182.camel@dirk 13:31:51 -> http://www.selenic.com/mercurial/w3c-talk/#(7) Cloning, Merging, and Pulling 13:32:08 Zakim, unmute me 13:32:08 DanC should no longer be muted 13:32:28 [note, slide 7 is animated] 13:33:09 +Sandro 13:34:11 so both Alice and Bob need to do a merge, even though Bob had done one already? 13:34:19 + 13:34:21 q+ 13:34:24 Matt: hg also has 'pushing', opposite of 'pulling' 13:34:26 ack tlr 13:34:29 ... pushing requires more privs 13:35:06 q+ to ask whether pulling needs a hg server running on the pulled site, or just read access (http, file:. ftP:. etc) 13:35:13 Thomas: am I understanding that both Alice and Bob do merges of e,f,g that lead to the same h? 13:35:23 Matt: no, Alice pulls Bob's revision h 13:35:31 zakim, mute me 13:35:31 Thomas should now be muted 13:35:38 ... so if she hasn't worked in the meantime she is guaranteed to get Bob's h 13:35:51 ... it's not uncommon to regularly merge back and forth 13:35:53 ack timbl 13:35:53 timbl, you wanted to ask whether pulling needs a hg server running on the pulled site, or just read access (http, file:. ftP:. etc) 13:36:04 Matt: in general it's very little work to do one of these merges 13:36:31 Tim: push requires write access. does pull work by reading arbitrary files/ftp/http or do I need an hg server? 13:36:36 Matt: see next slide ... 13:37:00 -> http://www.selenic.com/mercurial/w3c-talk/#(8) Multiple ways to share repositories 13:37:22 (an example of the CGI interface: http://homer.w3.org/~connolly/projects/ ) 13:38:01 Steven has left #hg-talk 13:38:14 Steven has joined #hg-talk 13:38:27 Matt: can put a bunch of revlogs in an http directory but this is slower 13:38:43 ... in practice, most people use the hgserve approach 13:39:21 +Gerald 13:39:22 ... "bundles" are highly compressed version of the project 13:39:27 zakim, drop gerald 13:39:27 Gerald is being disconnected 13:39:29 -Gerald 13:39:51 ... bundles use the hgserve wire format 13:40:01 ... tarballs can be pulled from hgserve 13:40:13 ... so browsable source tree has a 'pull' button 13:40:23 ... can pull raw versions of patch log via Web interface 13:40:37 ... any network filesys will work 13:41:12 -> http://www.selenic.com/mercurial/w3c-talk/#(9) Using cheap branches to manage changes 13:41:22 +Gerald 13:41:38 rrsagent, please make record public 13:41:44 DanC, you asked to be reminded at this time to check the time 13:42:46 Matt: the idea is that branches are very light-weight; create and destroy them at will 13:43:08 -> http://www.selenic.com/mercurial/w3c-talk/#(10) New features can be added with extensions 13:43:42 Matt: open source project have found mq to be useful in managing streams of updates as patches 13:44:42 ... forest extension manages 'subprojects'; whereas cvs has a tree of repositories, the notion of subproject is more difficult in hg 13:44:43 q+ to ask whether you can also brek out a subproject/ 13:45:09 -> http://www.selenic.com/mercurial/w3c-talk/#(11) For more information 13:46:05 http://hgbook.red-bean.com/ 13:46:18 Zakim, agenda? 13:46:18 I see 4 items remaining on the agenda: 13:46:19 3. The Mercurial SCM, presentation by Matt Mackall http://www.selenic.com/mercurial/w3c-talk/ [from DanC] 13:46:22 4. Fractal project organization [from DanC] 13:46:23 5. hg hosting, large projects [from DanC] 13:46:25 6. The toplogy of update flows in a large development system with overlapping cokmmunities with diff't access rights. Wrt slide 3 [from timbl] 13:46:36 -> http://hgbook.red-bean.com/ current manual (replaces URI in slides) 13:46:39 timbl, you wanted to ask whether you can also brek out a subproject/ 13:46:49 Zakim, take up item 4 13:46:49 agendum 4. "Fractal project organization" taken up [from DanC] 13:47:10 Tim: for a large project that grows and grows, will forest let me split off a subproject? 13:47:20 Matt: yes, if I'm understanding you 13:47:35 ... a project is a boundary where you sensibly want to do atomic commits 13:47:59 ... given two components in which you want to make simultaneous changes in an atomic commit, these should be in the same 'project' 13:48:16 Tim: organization of projects might not be so tied to atomic commits 13:48:29 ... issue of clashes does not arise so often in some styles of work 13:48:45 ... so management issue is to permit a single checkout to get everything 13:49:05 ... nice thing about svn is that a subdirectory can be declared to be a soft link to a project somewhere else 13:49:14 ... svn subproject can use its own access protocol 13:49:22 Matt: that's effectively what 'forest' does 13:49:31 ... a forest is a set of projects and their relevant changesets 13:49:32 Jean-Gui has joined #hg-talk 13:49:37 q+ to ask about splitting out, e.g. a utility tool from a big project 13:49:48 ack danc 13:49:48 DanC, you wanted to ask about splitting out, e.g. a utility tool from a big project 13:49:49 ... I'm not as familiar with forest, as it was written by someone else but that's what people are using it for 13:50:32 DanC: suppose I started writing a module as part of a project but then decide it should be split out. Is there a straightforward way to do this? 13:50:43 Matt: no, no easy way to delete old changesets or remove files from a tree 13:50:44 ack me 13:50:55 ... hg histories are more immutable than in other systems 13:51:11 ... the obvious way to do this would be to close a project and delete all the unwanted stuff 13:51:21 s/close a project/clone a project/ 13:51:38 ... in future we may allow trimming history; e.g. 'commits before rev X are no longer relevant', or 'commits outside this tree are no longer relevant' 13:51:52 -Kazuyuki 13:52:07 EricP: is it easy to write code that hacks the revlogs, like sed on cvs histories? 13:52:22 Matt: yep, people have been successful in hacking pretty low-level things 13:52:44 DanC: there's an API too, don't assume you can just hack files 13:52:46 not to worry eric, i bet there's a mode or will be shortly 13:52:57 Matt: several other projects have cloned the revlog approach now 13:53:03 ... e.g. monotone, @@ 13:53:09 s/@@/bzr/ 13:53:13 ... svn may also be looking at adopting revlog 13:53:36 Yves has left #hg-talk 13:53:43 Tim: describe some typical topologies 13:53:55 Zakim, take up item 5 13:53:55 agendum 5. "hg hosting, large projects" taken up [from DanC] 13:54:07 ... large numbers of developers, with subgroups who sync with each other but not the 'main' repository 13:54:16 ... others hacking with only email access 13:54:23 agenda? 13:54:30 ... what sort of workflows are established? 13:54:44 ... I worry about patches that are shared only between a subset of developers who heard about them 13:54:45 Zakim, take up item 6 13:54:45 agendum 6. "The toplogy of update flows in a large development system with overlapping cokmmunities with diff't access rights. Wrt slide 3" taken up [from timbl] 13:54:51 Zakim, close item 3 13:54:51 agendum 3, The Mercurial SCM, presentation by Matt Mackall http://www.selenic.com/mercurial/w3c-talk/, closed 13:54:53 I see 3 items remaining on the agenda; the next one is 13:54:55 4. Fractal project organization [from DanC] 13:55:02 ... so accidentially you have a patch that lots of people have but never gets into the 'main' repository 13:55:11 Zakim, close item 3 13:55:11 agendum 3, The Mercurial SCM, presentation by Matt Mackall http://www.selenic.com/mercurial/w3c-talk/, closed 13:55:13 agenda+ applicability to www.w3.org (largely asynchronous) and dev.w3.org (largely synchronous) 13:55:14 I see 3 items remaining on the agenda; the next one is 13:55:15 ... hash across the project but no single place to go for the 'tip' 13:55:16 4. Fractal project organization [from DanC] 13:55:19 Zakim, close item 4 13:55:19 agendum 4, Fractal project organization, closed 13:55:20 I see 3 items remaining on the agenda; the next one is 13:55:21 5. hg hosting, large projects [from DanC] 13:55:24 Matt: I think the optimal model is the linux model 13:55:45 ... a central person, Linus, who is the only one with push access to a central repository 13:55:52 ... most efficient if everyone only does pull 13:55:59 ... with push you wind up with two heads 13:56:16 ... second 'pusher' gets a message instructing them to do pull-merge-push 13:56:23 yikes, that means it won't work well with datespace 13:56:42 ... if a single person does pulls from 'lieutenants' then a push to the central repository it's more efficient 13:57:11 ... scales well; can assign lieutenants for subprojects and they can do pull-merge for their subprojects 13:57:32 Tim: ironic that the technology is Web-like and decentralized but relies on a centralized social process 13:57:41 Matt: in the end you want to wind up with one version 13:57:41 (well, 13:57:41 tlr, care to rase that now? 13:57:47 i would 13:57:51 (well, "relies" is stronger than what tim said, but...) 13:57:53 ack me 13:57:57 ... in fact there are many long-lived independent branches, even in the linux worls 13:58:03 s/worls/world/ 13:58:28 Eric: in the W3C case we have 'dev' that is largly synchronous and a 'cvs.w3.org' space that is asynchronous 13:58:41 ... we care that the code in dev.w3.org is synchronized 13:59:00 ... but the Web space cvs.w3.org largely has pages that do not depend on each other 13:59:05 q? 13:59:20 ... in the svn model that requires a single revision number for 100k's of documents ... 13:59:29 ... how would you arrange this in hg? 13:59:47 Matt: we currently do not implmeent 'partial repositories' where you'd ignore a subset of the repository 14:00:03 ... there are existing projects with order 100k's of docs 14:00:11 ... but you'd probably not want to use hg to do wikipedia 14:00:25 (this is what I meant by "Fractal project organization" again, fyi) 14:00:30 q+ timbl1 to ask about comparisons with Darcs 14:00:33 ... I've had a back-burner idea of doing something rcs-like, managing a single file but keeping O(n) 14:00:44 ... basically breaking out revlog but with a single file for management 14:00:48 q+ timbl2 to ask whether one could turn off the project-wideness 14:01:01 agenda+ comparisons with Darcs [timbl] 14:01:05 ... for a 100k document case you'd want to break this into smaller projects 14:01:12 EricP: perhaps year-month 14:01:14 1.75M resources in www.w3.org webspace at present 14:01:27 Matt: you don't want to divide by time, you want to divide across the tree 14:01:54 DanC: the W3C naming scheme lets you use year-month as a default naming scheme, files can still change 14:02:03 ack timbl2 14:02:03 timbl2, you wanted to ask whether one could turn off the project-wideness 14:02:16 Tim: I can imagine someone wanting to establish a [new] project at a given point in a tree 14:02:26 ... 'this is a new software system' or 'this is a tutorial' 14:02:35 ... making a self-consistent subsystem 14:02:41 ... but such a subsystem is unusual 14:02:55 ... e.g. these meeting minutes do not need to be synchronized with anything else 14:03:18 ... initial description of hg sounds similar to cvs 14:03:27 -Ivan 14:03:32 ... how big a change would it be to remove the project-wide idea? 14:03:43 Matt: pretty large change. easier to work with something like forest 14:04:02 ... or start with project with many subprojects and mark subprojects as 'ignore for commit' 14:04:30 ... this part of the problem space is very different from cvs and a little tricky for people to adapt to if they've structured their projects for the way cvs works 14:04:45 ... these hurdles can be surpassed but you do have to think about things a little differently 14:04:52 DanC: thinking more rcs-like? 14:05:04 Matt: yes, if everything is really independent then you probably want something like rcs 14:05:13 ... wikipedia only thinks about changing single files 14:05:41 Eric: on a human level we frequently manage file dependencies 14:06:21 ... if you could say '{...} are independent by default, {...} are mutually dependent, ...' that might be useful 14:06:29 Matt: that's blue-sky from where we are today 14:06:40 Zakim, take up item darcs 14:06:40 agendum 8. "comparisons with Darcs" taken up [from timbl via DanC] 14:06:50 ... if we wanted to support wikipedia with what we currently have we understand the changes but we haven't worked on it 14:06:55 timbl1, you wanted to ask about comparisons with Darcs 14:07:17 Matt: I understand that Darcs is (a) orders of magnitude slower and (b) magical 14:07:29 I really don't see how the structuring into projects makes any sense for our datespace 14:07:32 ... has nice properties for cherry-picking in a way people seem to like but that I believe are problematic 14:07:33 http://darcs.net/DarcsWiki 14:07:38