[Monotone-devel] Issue 138 - monotone should have a reference card (monotone)
Hello, A new issue has been created and assigned to you: 138 - monotone should have a reference card Project: monotone Status: New Reported by: Stephen Leake Labels: Priority:Low Type:wish Description: like http://www.cs.put.poznan.pl/csobaniec/edu/svn-refcard.pdf Ideally, we need a formatting stream for the 'mtn man' command that produces a nice reference card. -- Issue: https://code.monotone.ca/p/monotone/issues/138/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] policy for FIXME stuff in wiki?
Thomas Keller m...@thomaskeller.biz writes: Am 23.01.11 13:30, schrieb Stephen Leake: The wiki has several things that look like FIXME comments: For example, in ReferenceCard.mdwn [...] Unless somebody worked on this recently (and with recently I mean for the last 12 months), I'm all for removing these things altogether. Especially the referenced page contains no information which are of any use to do something like this. If at all this looks more like a feature request and somebody might consider adding an entry in the issue tracker for that. But given the fact that we still have no graphic wiz around, it will reside there unworked for long as well. So yes, please go ahead. Ok. In this case, I decided to simply delete the ReferenceCard. It's far from complete, and I find the online help much easier to use, and certainly easier to keep up to date. I added an issue for it. One approach is a formatting stream for the 'mtn man' command. -- -- Stephe ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] nvm.source-tree-cleanup
Hi all! Richard, Stephe and me polished the above branch over the last weeks and got positive response from a couple of people that it works well for them. For those who weren't following the previous development, this branch is basically about moving stuff around into specific directories, i.e. we now have a dedicated src/, test/ and doc/ directory and the in-tree documentation has been sanitized accordingly. There are a couple of minor issues left which kind of block the merge back to nvm, one of them is the move of some innosetup-specific resources out of src/win32 and another one deals with HTML documentation. I'd still put the whole branch up for review now already because I really want to see the work merged back in nvm to get even more feedback and also to allow third parties (debian for example) adapt their source trees according to our Makefile.am changes. So please have a look at the changes in this branch and give us feedback. If you think it is not a good idea to merge this into nvm yet, then please also tell us. In case nobody places serious objections I'd like to merge the branch by the end of next week (Friday'ish). Many thanks! Thomas. -- GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en signature.asc Description: OpenPGP digital signature ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] nvm.source-tree-cleanup
On 01/30/2011 05:08 PM, Thomas Keller wrote: Hi all! Richard, Stephe and me polished the above branch over the last weeks and got positive response from a couple of people that it works well for them. For those who weren't following the previous development, this branch is basically about moving stuff around into specific directories, i.e. we now have a dedicated src/, test/ and doc/ directory and the in-tree documentation has been sanitized accordingly. There are a couple of minor issues left which kind of block the merge back to nvm, one of them is the move of some innosetup-specific resources out of src/win32 and another one deals with HTML documentation. I'd still put the whole branch up for review now already because I really want to see the work merged back in nvm to get even more feedback and also to allow third parties (debian for example) adapt their source trees according to our Makefile.am changes. So please have a look at the changes in this branch and give us feedback. If you think it is not a good idea to merge this into nvm yet, then please also tell us. In case nobody places serious objections I'd like to merge the branch by the end of next week (Friday'ish). #include's use relative paths now, instead of absolute (base.hh in src/ and ../base.hh in src/network, rather than src/base.hh everywhere) -- except config.h is still config.h (and since it lives in the build directory, a relative path ../config.h or ../../config.h won't work for it). I guess that seems reasonable. A number of functions now have their return type reformatted onto a separate line, that's perfectly fine but gives a bigger diff to look at. make distcheck fails, apparently because make doc/monotone.ps fails (but make doc/monotone.pdf works fine). This happens even with a writable srcdir (ie, not limited to distcheck). -- Timothy Free public monotone hosting: http://mtn-host.prjek.net ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: [Monotone-commits-diffs] net.venge.monotone.source-tree-cleanup: d54c8c17eeebbe7dd6bb30d4d10996db79de24f2
Stephen, with regards to this change, I'd like to know the background for this: * Makefile.am (doc_monotone_TEXINFOS): move copy-html-deps copy-pdf-deps out of this; they must be files in the 'dist' target. Also delete $(EPS_FIGURES); doesn't work on Win32, not needed anyway Most especially, I'd like to know how having $(EPS_FIGURES) in $(doc_monotone_TEXINFOS) doesn't work on Win32. Not having $(EPS_FIGURES) in $(doc_monotone_TEXINFOS) doesn't work when trying to produce doc/monotone.dvi (which is needed to create doc/monotone.ps). The optimal thing would of course be if we could have a line like this to express extra dependencies: doc/monotone.dvi: $(EPS_FIGURES) Unfortunately, automake takes this as an override and will refuse to generate a doc/monotone.dvi of its own... In message 201101281209.p0sc9bmk035...@monotone.ca on Fri, 28 Jan 2011 12:09:11 GMT, c...@monotone.ca said: code revision:d54c8c17eeebbe7dd6bb30d4d10996db79de24f2 code date:2011-01-28T11:56:05 code author: stephen_leak...@stephe-leake.org code branch: net.venge.monotone.source-tree-cleanup code changelog: code Clean up Makefile.am for dist, win32 code code * Makefile.am (doc_monotone_TEXINFOS): move copy-html-deps copy-pdf-deps out of this; they must be files in the 'dist' target. Also delete $(EPS_FIGURES); doesn't work on Win32, not needed anyway code (EXTRA_DIST): renamed win32/README code (doc/figures/%.ps): improve dependency chain, move copy-pdf-deps here code (doc/html): move copy-html-deps here code (dist-hook): add copy-html-deps copy-pdf-deps here code code code manifest: code format_version 1 code code new_manifest [82acd2ae8a0f450ece4ab4a36cebe4b886128c44] code code old_revision [3627249c28749684bf092c5f1eaa5fa6788c94b1] code code patch Makefile.am code from [cfc006c165b6e3eb214d4c176ce9217fafe69265] codeto [6d33b4f8c99a9898ee999417e5e6141d0b46f2a4] -- Richard Levitte rich...@levitte.org http://richard.levitte.org/ Life is a tremendous celebration - and I'm invited! -- from a friend's blog, translated from Swedish ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] usher 0.99 release (name-based virtual hosting for monotone)
On Sat, Nov 20, 2010 at 02:22:37AM +0100, Richard Levitte wrote: In message 20101119201102.ga25...@topoi.pooq.com on Fri, 19 Nov 2010 15:11:02 -0500, Hendrik Boom hend...@topoi.pooq.com said: hendrik (2) Is there a comment convention for the usher config file? comment This is a lengthy comment The comment has to be in quotes? Are newlines allowed? Should this be documented in https://code.monotone.ca/p/contrib/page/UsherDocumentation/ ? -- hendrik ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
