[Monotone-devel] Re: [ANNOUNCE] monotone 0.34 release
Daniel Carosone wrote: On Mon, Apr 02, 2007 at 07:18:23PM +0300, Tero Koskinen wrote: Apparently Monotone 0.34 doesn't compile on OpenBSD 4.1 (i386). Nor on NetBSD (-current). Strangely enough, on FreeBSD-6.2 it does. I'm preparing the PR to upgrade the port... ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Messages in monotone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alvaro Herrera wrote: That's because we're used to the more widespread plain double quotes (). But the cool guys say different. For example, check [1]. (BTW this guy says that these quotes should be used in french as well.) The Debian spanish translation group agrees with me [2], so the «» quotes are used pervasively there. I do that as well in Postgres, after extensive investigation on the matter because my escepticism mirrored yours. Don't know for spanish or french, but in italian the «» seems to be more specific to quote a text or a piece of speech, while '' is more correct to quote a single word or sentence. In computer science speech I'd say that: « = push context, create a wholly new context » = pop context 'x' = take x from a different context and talk about it here In this regard, '' seems more correct to quote a file name to me... (in italian!!! I don't know about spanish or french, it may be completely different of course!!). -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF/P+HAAoJELBiMTth2oCDUu0QAIGYkKsfljEOIjIMC+DqxpMS nSkeReVVo+TT9bD5Y5udNaUTF8M0kiWb2/E1GoppIJEqmZhytokAiEnbsG+US4cQ 7GppTbLULNNrJMKd5LvpqQQSbwHuA61Nfrtq875B07qLmKgx/EAUEpU6GnxOJtfN jchjHiycj6Qpz6aKrd2By7BlfFuzdYzHz7Qb4gI75q6EbM1qsIL8K8NdHDuHXrHG T0RGvi6xN9l3SvQdgFaGaYU4IPa7BcRY9Pla7iD45GIV/sEJ65sD09ZeQr/Y2sBJ NrXHibwwAKsguR0G66f9D9B1s8gibG55U4vIglxLWa1g5qLMSfn2nKnSh4zQAsQd NIqMReCn8q+3o0HLrKQHys/mN1tzdB2XKtN2WMwC4xkYqcZJof3oaZq+WFF4WxOK WDxdFi4dyDQlubZ5iwH35iP9e+aYTydPv6ARNOxB5ZLLodBGtx0ZAKlmpirVEP4L PK5wLHBwEY6Y/7TH/8ejw6FgRBMlAnkBQ9HMTBaHKnslZVsNMEEBqqV2NS46VxXa uST6S3RulaCszd5MdYsDLm36i3tv9kr29lGV1zw12QsbLCpA/BV7vdMHHp8lkpQA HaGOHeLJ+MPTrT72ENT+QZmNWcR4GRjDAcDqMtISaUI7XuommP+49oS2/UAzoT5L p21IHaT5HXxM9bsWz+vT =J1+v -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: bug with utf-8 converts of log output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henry Nestler wrote: 'mtn log' stops on non converted changelog entry, if the current console is not utf-8. It works in a utf-8 terminal. What OS (and version) are you using? Do you know what version of iconv does the system use? PS: there are already patches in the trunk (landed after 0.33) to only use the translit feature if available in the local iconv and outputting question marks in the worst case, instead of untransliterable characters. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF+QccAAoJELBiMTth2oCDs/QQAL4kXGDza/cRbF4Qvu/nJK05 NHHocb4uk79nCoye/wcDrXbsOKoyQs1iCgouVdsbz4BV4YFchjNwW1MdQ5ekM3Qb 6aU6mtkEdOQQ2XvY6gUFyp7b3VMBmc78y+/NA9V8p/rW96eZ4if18GYRKGgBbi9D qNCjVPP4Q7Rth5FJgRiGcblefiKP+H8hsaSAJhDMM/NgMzHStDVBP8mQqwbi5bGh 1qkETChk4kmPt/ghGyOIUYSnxmZ3VSAzQbEVxn2+bPPDyIx5WonVpMHB1npggb6R 3ZB6HNFYR2Z5H7mvwSkIBJVi5Qbr2wHg4OrqeuS0ZCyp6dbiPqzl+ySiZhuky57y MsT829qIP1uWxMynAGhjQK4JBVxld18gNZ/GqkFwx11jVY6HJ0bzKcj0SFGhV5Io WrgFWA/C7VwF3gCs1bXMndbJjlBpc/LO77P+lN0mNfSQCQvjueHcAwxNhn7ohMrh 3nIfoHsQbAqK6CY3gl2TTbcE8q/RO+ebUKPctRwty+gCjAxHfKxrllv59uk5G3nZ WajVsz+xHYG40Zb0ZVx4uiviUo1cXxmcTSRGtGBFNabjo03jWV4CwpfnSmNKGF/m NeApsIoESoRYKPZo/qJf4pntinItCDV1tQwrYngqFfX8iC7Yu1U8ViRFTU7GuEJv +4kClI3+5xwYV3Um6sUt =mgTN -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Messages in monotone
Richard Levitte - VMS Whacker wrote: having worked with Stéphane to bring the French translation up to date has brought a few realisations, both her's and mine: FWIW, I encountered the same doubts. - File and directory names are sometimes quoted, sometimes not. Same goes for other strings as well. I recall that there's been talk of cleaning up before, maybe we need to do so again, if it was ever done to begin with? Maybe we need to agree on quoting or not to begin with? My vote goes to quoting file and directory names, since they can have spaces in them. [Richard] In Italian translation, I decided to always quote filenames and never quote revisions (can't have spaces, are quite clear to the eye, and easier to double-click in some silly terminals). Never found the will (or time) to search thru all the sources and add quotes in there, actually. BTW: what about using `' instead of '', like gcc? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Messages in monotone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ralf S. Engelschall wrote: So, if Monotone wants to be both in the range of ASCII and still typographically correct In fact, in the Italian translation, I'm using the 'correct' Latin1 characters, as Latin1 is strictly needed for accented vowels anyway. But nonetheless monotone has to be ASCII IMHO, for better compatibility even in the broken (but quite common) case where the environment of the user does *NOT* reflect the correct charset. Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF+TQfAAoJELBiMTth2oCDmdcP/39uAnmUaJChQVSw5X3vocI+ TlZZuhavuh62Yr5eQiKEUAoENj3sq3DhRwqBi3NjXemmNw+4WqzXJeGJ0LFNcCFE mBX5YW50i4Jr+theWWOujHPiefP0kSh1Nekf39inrvZAikJeP26viSR5dPX6xnBS EsAmpp/oV5xfx3NPsYtTtCvn8W5tyeBzz06iqQn6xV6ovP/i8lgkLW7wOxlmeB0T k/BPGEEl+rtNLzNAgK8wvanN01bqKLHW4dhWLR0B5I2qr6KwbPuufL5IueRAscZf gDf9QX6UYpVJ+IoxuwLy5stfGPtw+rq+ubXDxpFQvZbz/a6kuxRA3rnjAK0VFh8D i0AzOM/BIkSDzNPfyMlyczO0olVu+XQdrpSzT8aqeU3WbQyw0ISBoy4BuPokPM+H 58Tvsg58rRjxOLUGVyaL6qbl8f1KZX/4XCChQJC5CVnLEpjA7r9ggIKl3viWc+0o lvOnLuS3zbb0LQmtnIFff5fDcp2eOqGw2ICFilXZ+R0T3LIdbLpvMyAnyg1AVDUF h8WVx/k1g6BHgYE7pcmgZWneNkxBEuobk/cXeo4NjG7FrjT4btxGKYZx062n0mNN I4zg/iH7LHXuHylu5qorIiZ/e0VsC4GDjgxNdMzElxeR9Yv+ul2MXpGnRAxfKiyv EQlUmfcd0tfPYTOdRhZq =OUXd -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Messages in monotone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zack Weinberg wrote: On 3/15/07, Lapo Luchini [EMAIL PROTECTED] wrote: In fact, in the Italian translation, I'm using the 'correct' Latin1 characters, as Latin1 is strictly needed for accented vowels anyway. You mean « », not ' ' or , right? I was totally wrong: I'using ‘ ’ and that's not in Latin1 nor in Latin9, though they are in CP1252. They gets automatically translated to ' ' on my Latin1 consoles (I don't have any system with no //TRANSLIT capability to check them... I hope gettext does TheRightThing). « » really really look bad though... Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF+dEhAAoJELBiMTth2oCDit0P+gKYwUPIyqBp/SBBKUsAawDo o4T09xfI5opcTxCTzA07yp6pC8QnsbLWTXKEht31CUxtE8rDfXgrpRkbbH3Ckl1v sKjFNAGWgkS7oZpOfEYnicMuXAb4OgMtKtiaebnAxrR0Ruu3ZFfgC9+azYMSqCat 6u+Fz80GFRYKqS3P9Dy3g4LYp95f2So+7fWyXaJYBFT+x9+CXEZOZEF3VZuH91PY QCXcTue4ZdZFoOIcjpLZOga1cSvA7cJhZZXrSrHc3qFKiBkexOX1UuEULtcpgjpG TdfwY4VyDc2NLL3ML3zGr4ZQ43zrOm9oF4nghpzoxFML+CQNNg6o0Oj0HqPjNMhg EAUUYIyTpJU1+XZ7MXZ9RcJeh3mUh+NNLxkXxJ+jcwr0Qb7mkEO7hwtPz5mrOgRL zXnpP1yZvnSo+59h6UcXx9+Yb5RiuScZN2ntsoLfw2D8J3gjhADU7GTbEut4UDXe tIaQPh1ftoGF+R0QpzpeKLIsRr0Zn3UsAgxZBCqKKqx9WlffCb5AUCz2ZhOu3C+x f1r5i7h2IY3tJPS2n1qRNTgr71OhtB6yRKX4v5ybNXfCXjDJM9vpEwEcfPhbq3E1 YOmS7C9O0dZ5jBFLZMV3D88ilNQU1s0XT/cKBN3lAitCHzNB01DFhiw3GZQBCF8f Uomc1B080HHbH7V6hmFK =PF0y -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: bug with utf-8 converts of log output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Henry Nestler wrote: Have SuSE Linux 9.0 (i586) then I fear SuSE's iconv doesnt support //IGNORE//TRANSLIT (would probably work with //IGNORE,TRANSLIT). I suggest you to try the trunk, or at worst I could send you the patch backported to plain 0.33. As a work-around setting the locale as UTF-8 *should* be able to not translate it all (though of course it all will look messed if the console is not really UTF-8). - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF+dHbAAoJELBiMTth2oCDa98QAKhHIjRxi4QFk8wemFQROu6Z GAnV5CEj3ZclVevjX66nMQjjaxJMEYDtkAFNNhyYJhmjuotF0x84J/sl6Sefcqgj Qc86suezJUbhkhPUdThoohfu6t1Fwi8kdImyquh99+TavwHo/2qYyDREVfOnAwYG LM3yf5v7Eu0/GN1NR4obfKPuV9Hxo/N9Dxi0YnZj/31yLji98TcOV1kaQyqrlvM8 Zl1dgIJAMMnbi65jeltmM7QHdDwS08CtcV+vNk7UmKzJYIs8uROCLOo/HOoQuDGb 0kiXhcjgfz454Is3M5OSf03lqhcoCSyV4GdcfMzUoOE3Sp67jT9dWJLEAjaTQO/p bHF9416iY7r0npztYTsEqtwsvp3bk83TeM/aYyGWB6Ur8eMTr86NNmlItn9+OCm3 AjFXHU8bayDZmqnrsuRQJbe9RtxrNaJvsHPOW8V14hBDW8btaryyfqMzJ6isx3qy R3DY1GPAD3SjgUjvEALKwKdxR1zDuyHD7nYQ8gnS2XhzOW+1nJxwBd9eKfqIHkRt 74dHtMMyYiMsWnjHj1mrM7xIYS3DlpYh/RM7uVAdO5ym/9H63+hdgHXRF/XtL9Ly l7xDd0YTDNEUEDv+IJJqJUyLQDOg/LXUN0iOgIjad2xYM38w6UQIkHlnip0VU20g zRgLixRH00L+kQcD/2wy =RqiV -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Messages in monotone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Levitte - VMS Whacker wrote: lapo « » really really look bad though... Not in French. Trust me on this ;-) In Italian books I kinda seen them all (“” ‘’ “„ «»), but I think the first two are the most common. Those Who Rule the Italian language say [1] that: “” «» are equally used to quote text or speech. ‘’ are generally used to quote a word or a sentence. The type of quotation used in the newspapers mainly depend on internal editorial choices. From this point of view, and from the one of major availability, «» should certainly be chosen for Italian. Though it still seems strange to me. Oh well, I'll talk about it with the people that help me with the Italian translation and we'll see. Link: 1. http://www.accademiadellacrusca.it/faq/faq_risp.php?id=5534ctg_id=44 - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF+j+IAAoJELBiMTth2oCDYdkP/RSmz/nfD2mdtyQnSyfW2vPg mrrtT91JzC1NFkWKxC4NTGezin5nokOR1XqfpYmwHmh43lP35l70MSMGpQt5Z0ct oFXAsMOeSbk+Egpp50TNbaNDAHvq9y6kqxLpw1wQ2Ed9TQPgitimgkc0pA6/ghgh PDHzGRGd01zrynelM2hOB/PmIRKE5YOsSEFgQLCLbSzVR0nd696UhMlvtSOElPCX V5+6L5rH1WPcjtD32PNeaQIGzPVZK60RVjMpXkgIxAz9R3bpT0vOrCsZ4f5Tj5P9 0jZ6Ra/yKt9vU45CT5LLiQeWuGq2Zoy0ltu3yOi45teh1bkFKMyj83Q+mxgLZZw1 fa/eK7VuJIZcyI0HDi8/nalliY1gpqclrx5s3+IlQIDDAuHszBxh07Y0vMmEs4OY Ur3ek8EeClFxFigBmintiVtRf8+X0qOQmoOxq34+MRp1+jO36CHzSamRN+ZarUSa HNQE5wkLrA2KID9FC5cdlkzYpLdEY2ji8ZxirSNNrBkhCP2ROEcInt4ZuzP2SfrJ Jw+YgIY4n5H9XkGWVVu5dIJ5g5eQeNOo/bMwSGWMsAxGqOpDBi3h3lbn6eKkFAb4 Y7HsnUIkox77FfYm01QL1Eo4zLjwt+5pbGaPtF02IC0XSWnRXjgxU1SHxO7tRy9v 5xnMnlHCaJCyVgTAS0Qv =myD+ -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Translations revisited
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: We don't run intltool, it's part of a translator tool suite. I guess I don't know for sure if any of our translators use it now, but at least one did at some point. Personally I only use (and suggest strongly!) http://poedit.sf.net/ which is capable to import .pot file, to automatically fuzzy translate similiar string, has a translation memory (which can be fed with all the .po/.mo found in the system) to help find fuzzy translation, and is overall easy to use and nice. Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF8+tPAAoJELBiMTth2oCDYLUP/1bKij5vJmIKKJN3K0pv/j8m Eku2JBI5RHhRdYej5ZPpwzLY0mbVjg+Cw7d3XGTYyiEVzkHalf6ztK5KNPFdFjs0 G28q/elRrKqfFeQaYbpy+Ajoel7dDDpOmQzqkT1EgbAlaNP092PdHWS3kCpBNTai Q8cL0PSjds9TtsnouYJuaRw/ziKWBjtKPbDu2zP5vxW21Ls3bF51FwasDyQD1gPQ uNy6PDRKIMAkjqV1e8IDWg3meHxXBocVM3uoHwwy8RWe6tAJlGS55vv78VEmYH4y 4JS21FN0FG5qy1ylemF6ix3hAHeC7CAdRE6U+OIBz+J6bZm3xu+zCgnRZeQz2nda 01a9D5TUoRzAA+ZnIR06lUFcqo6vgKFemexDdeAc8dMCe0LOjQCF/p4lB54WvIU1 E86aF0TjP4IHYH/hYaFPuI/toH9yvRv32bDiYWOIsna0Np3F2MfFnS9aHwhrrfCe Sn4KUQKZEKNmIwpth5XrSy/6P+qOIYpb/Vl3FgRwQwta5oiJnTudXxU89ppC8MO+ aOVSrnSZR7H0uiquBaRR5cQrXScwBSZKO6TF/1/UtogGMyMZ7l95+aUDWM5DOsot rIAAfpOiSeX6Yr7oN5/yEQcR2sKBd+mIFszpn4ItMxr5Sh++uMmXrKfATjfM66FY 0moPoUsiToUvTnlhvJCQ =hXLS -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Translations revisited
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: But how does it go about updating the .pot file from the sources, i.e., finding newly added strings to translate? That's the question here. It does not ;-) I usually call the make target myself. Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF9Ij9AAoJELBiMTth2oCDNfkP/AlYbubed9PB5aBJ+/bfV69v ukKWDiEVhLxU64ptBBJT463/5SA7TfncQhTCDHsrwMQg51GJNdgx/4hd3vXHtHbR HevyMtLWVyfdp/W3pfh2691N/JhaS876XLkwJeuVzyjuoVak91e4m9gdGjpSsRf0 gqIi03sRFbbZNzmmOit+qOW0yRwOgp98Y9CkLPx1gpUThFtGCDA33ZEX8HOddu+a RGxMjdh0KhmYqRju1q8CfPoX8+3SUn66ZfQWgWvoiSYz6U2FyAQ4p2Rnl9twjmnc 5XH+UjNod0cJRwhs3x6WgYCxmQlJ6ylPOkkaGU+FeIu8IPwh50SEPqHrgTQw2uv0 3sDPlDGNal0r81UQ2msx7z5Il+/YGF6qTDbEJsrVFGkpMc8wftQwOhdf4F3tKTRt 2MEc9HAbjkKN7QbGAeWTcWlT6mV3w42FxnDPbhm+GvfWjMNoEO8DLvKQPNAxOobg xwiezaTeJg3v9LIxnfSxZP7epHbgOcA/MOFqJX6xq24wMGjc9PJudS997RCeZ3Zq u+RvRliv8D/gxXhl/6dbjMNV/TXvNJJq19SFyYqq9N1fGeDMHYqOJNPgsGUBjrLW izWoYefElI9Rrow2OUtr9+7Othm9i0E/cxdTMEINJ9faHsCaU6HhZH/azvR+jB7w ezNK6zVgwRLDu+cx+lAJ =VB15 -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: cvssync-refactor
William Uther wrote: I'm not sure I can separate these neatly though. I think it is easier for the bad keys to be an issue if you're using ssh as the transport - it isn't checking the key of the person doing the push. I think not: the key of the sender has nothing to do with the key that signed what is sent =) (e.g. when I do push my revision I usually also push the translation fixes made by my mother, with whom I sync'ed eariler, though she doesn't have write access) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Files in contrib/ missing from 0.31 tarball
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: I don't know about require as an official thing, but it's never been possible to build monotone unless you use gmake. BSD make doesn't accept our Makefile, that's for sure. =) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF8YjJAAoJELBiMTth2oCDtFgP/3sOGtyl7mA48SEDQLpVxas3 LBm6DAx1sX58xzuikcQeYEKoEq1CGPCeOl4kmF+wuI079xZVdra0q7raOlCRe2TZ 4ie5suIR4cvEK4m8oXsJzKCbPenI9r6HClbpyBphtjjwyfQwYZnqx1Qx68dQUCS1 YtT4TyxgBNWGbuW8TLWRYq4as0u4FQ26iwfdhf0xHXaaevRKSi/VjcKOIBRrcuYF NDQYo5D4vTWcru5HWZBSx7P5Y53n3FExo1eLRqYB8yjBT7STo15JYWp5ETX66Fcr SbSEjaIKrRewv6zZh8w0dyvqdcUlmLjWTh4p8gBrHs0a0VPLy9WmswWOm/09FdVD JCnHcqybmrlj4WC23oTK74atOw4zSg375nmlvxFKTLbWwbjwB2SGJmIigFn7cb/u HoOAG73sgevLaV3CCy1LZgADwhKoyvaNvtqFAbX8ND9uCqOzbPTq9um0nRnVtbRH Mh+ehgLcSYVqsex9a5HF6fAYBX9TEQHz9RCVwWCs7U0QnXZToDlziMBdZKk1TsEh 0ZxNyAznSjNCaZNkuNzoPv6HP1zzY+eI3CrvHhkLWxY8qOd+8z85d2alC5/dqHgX JZrYdwM1kR+JuskWvk0gqnPNntuZTgFsWcSbPKXmXU5u+eFgkmwQh9bLrGo66a1K S8sdvR9QOd1e+RtI26Fv =YUao -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: avoid iconv differences [Was: Tests passing!]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lapo Luchini wrote: someone may better review this: mtn diff \ -r 6d564a26acdcfc5b1e40b0d1102d550933c76244 \ -r h:net.venge.monotone.lapo.i18n With no (new) errors on both FreeBSD and Fedora Core 4, I'll land it tomorrow unless stopped :P Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF8YtMAAoJELBiMTth2oCDIX0QAI0j+CPpmQ09KNnxvVKrIZg2 mRnntWYEgv7FOlvkba20mOu7wlheDivqMARgZxnkf9XHWq/DF9BFk61/zyCDVvor sdi/MO2MdfJUmVlf44SWQKmVRA/KxeG4pzy+6XKibi7tRjh40Juqf0u7LWqKHw+V J/DYlMQGwzNUbXZ8f5nC+Q/goSpWbhI59T92nTZW3/bmu0fg2ZvJocG7JIHKxgf4 BEqeyakqG3BOVEN9iG/Phg3MyzAUcY3fiD41YXLu+QueuplwrfhXffQOoax7FnB1 tz9tXVkZ4jyDOeZW7Ri4SOozzIFeM5L1xBrXifSufHWD5S2ohOafRP/Y1imbFdg/ qxJcTukUFPVnGXYl58CTsNk7NzMdTZkp1DA86LLaEv1gdAhsjLF21J5RG7TYmVog xFMCQ9wG8+6ICafowz66y4wDdIlvvLPoZ2maKpXW3RJz15lWUleoF1eh6h9srDSP WPKfYYYMufWUjbMStshLRtS8JfnxmIDgmEPxLmQT8UKR5oIBDfIduoF1mglDCwYh 8Kc1O+uAXKDq42/qvWtHdOSop/PUWhtXV6LqAPL89G4UFGNjxPiRO97pECU3+T2F n8EQA6dLaS8BIZICk+BP9Rfd25SXZbbzCv9s+RjEBwb54uDU1tcMKs4HhImVExIl 11nwyhl4sIG2Dx4opXM6 =iXtd -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Hook for source code beautifier?
Boris wrote: If I want to run a source code beautifier automatically (for example when code is received) is there a hook I can use? I think the code would need to be checked out first, formatted in a workspace and checked in again which is probably not as easy as telling monotone somehow to use code beautifier X for newly received code? Commit hooks are executed on the computer on which the commit is done, so you'd have to distribute the beautifier to every developer too. The is an hook on revision received by netsync too, but at that stage it's too late: once committed, the revision can't possibly change without breaking all the digital signatures. Another approach would be to have a computer constantly sync'ed and updated and execute the beautifier nightly, with a clever script that would commit only if something was in fact changed by the beautifier. It depends if you want ugly things to NEVER creep in the DB, or you only want they to generally stay close to not-ugliness. Notice that this kind of things don't usually play nice with merge, as a beautifier usually changes MANY lines for LITTLE reasons... (this would be an argument to use the on-commit method) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: [ANNOUNCE] monotone 0.33 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Levitte - VMS Whacker wrote: Monotone 0.33 released! FreeBSD updated this very morning. http://www.freshports.org/devel/monotone/ http://cvsweb.freebsd.org/ports/devel/monotone/ Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF7aOlAAoJELBiMTth2oCDfz4QALgBt6i22LQmSz6kyVIoYFk8 sktEkPjFhhU5H910PNzTitrMN3cX9DyiAF1b16XISDs45euJxsJSukKVH84m/6Ch 6i5cjXh9jJcdsuLv9n3yUZoVToJ9KwsFiGB4/UJumyn2ApRR1UKiy/nxrI5gEmOc D1xgKjldmyQCoEkPn7Fj+QemsVWomROtW8JjYImHwTmS8EhFztmW0HGTBHpKKI+Z 5p1FKtyAu9+CchOGp1wpo6x8eiGeRqiN/m+yYNFs+LvvsmbkYlZu2g1c+3kfVIZH IR5tEFAAepaneiZH0WpmLReb+32d3CzmA1q2SjlIzqHa60pcPZQ4kUqtyTQlVTzi VAmZ6RejVXt6+xUn936YXuAhsfVN7Ji7Ru/owq+7ziUWKZtw7w3aaAWwPVPRKgNF MYEKLwUka28su6N03ClDo7fPBrAQiQhTFcYPN0crwz6cQV8gSCUaw/sEu11ov7wh Nu528jMP0fA+0NKfaQpxMPgsRyJT/p6Z/L3EXl0fYWKVi39hVkEOP5kTSApjH4UQ tbxpsGvNOO8Eh7KnWyUD6FfzTqo8MaIIv7MsJTmOveJdCst0KnZvmsSFeQgjEtjY SF1S6M5iqb5koZ5AvAcPtVbIJtzeUyzxA02+e++K56xj4TI7HOyEYvjgHsAwfjto ULfoeN4QuuQ3pgYyfMkS =VAZo -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] avoid iconv differences [Was: Tests passing!]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: I guess we always want question marks, we're going to have to insert them by hand in at least some cases, and we'd rather not deal with all of this insanity. So maybe we should consider: -- try opening our iconv handle with //TRANSLIT -- if that fails, try opening it the normal way (to account for any systems that just don't know //TRANSLIT) -- when we actually process bytes using this iconv handle, do poor-man's-TRANSLIT handling -- whenever iconv says EILSEQ or EINVAL, then dump a question mark to output, advance the input, and try again. This seems like it might be the minimal necessary-and-sufficient code? Seems a good clean approach to me. I'll pursue it ASAP (a few days worth of bus-travels from and to my workplace). I have to remember that skip in this case is not ++pos, but rather pos+=utf8_char_len(pos); (for an hypothetical utf_char_len function). Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF6DNEAAoJELBiMTth2oCDyh4P/0H5JtROQyebTb7tjAqJImwG 5At35OAYObJIvWjrjfbu6rBHSThrOqKiAsp8dDyAeixoFDSdxxCyXmBN3vOtvUun lOXylL3MguYCcnR+3O2tSQxg2/p7ja8PWuEmy29qSQg+H3GpQM9rZfrwp6aHLyFP UqgrvPkL4PQK3Y/dZ8wLuxw9L3BNpai9LRHQ7zFOd90bOq5Ena6yGiaIPV+9C92/ grGDYm6ovCz+sSp2OoZstV0NBrCio2u+P75ha6Hv+Kluca3I7BlU+Bqbi5i7QXPo ythRvqIAd3X/Kl4tR1FwGnHb5H6dvAmZ0QdVdABLPOCYfl5lg9GvgXBmdpeB/1Bc HN1Oud4N/wDpEtdbGaBDoZnrdb+DkHhG2OUUAgiotmdfBd0cg8sqM/fTTebWAGBD pCnV2FwYnPIvlgsl6nhU3jfS2k8IPodS6FraEYbseaZn9mcudSQt9oozGQ+JomIf 2vcG/15yE31cUcW9YN0ovVFwuH7+IiWCdDMd7k4woyiJHM3QjBp5E/M+QYH4o0J7 518eCiMOcMcE2WdHi1d7U3oCnSyK5Cb0B8Bx9UxGJWl6mU9/Mz5Hslls/KZoBDGw kNrN6yXx76Omu2dA575bWB4x9Qyb1HVxJqEmrCCDbur346FOY3SSzoMidTkA0LRs Lz8mdk0Lgt8hCSbsh8qL =AIG+ -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] where to put a (default) database? [Was: clone cleanup failure on Windows]
Nathaniel Smith wrote: iv) Don't put the db file into _MTN? It's kind of a funny place for it, seems to be causing trouble, and I worry it's going to totally bite someone on the butt when they (spread out over some months) do: Certainly funny and counter-intuitive for mtn users (me included). OTOH that's what Hg does, AFAIK, and probably also Arch friends? For CVS SVN people just thinking that the book keeping directory contains the real stuff is plain crazy: they know only the server contains it. IMHO a better default would be ~/.monotone/branch-name.mtn... or at the very least; that's what I usually use. ^_^ (usually restricting to first 2 component of branch name, e.g. net.venge.mtn for mtn, it.lapo.mtn for personal projects...) Small poll: what database file does other people use? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Tests passing!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
This fails because it relies on //IGNORE//TRANSLIT (or
//IGNORE,TRANSLIT, as drepper claims - whatever): gnu iconv feature
That's my nvm.lapo.i18n branch fault - I definitely have to check that
in configure and use conditionally. Will do so tomorrow morning on the
bus (8:15-9:00 CET) and hopefully commit it at work shortly after.
This OUGHT to do it, but it doesn't (no wonder, because the error was at
the LAST character of the transliteration, not at the iconv_open, when
using libc's iconv).
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJF5rUfAAoJELBiMTth2oCD7pMP/1qvOIPJAup2c9NThEfLjUSM
U1tDVxXGVyT/m1t+4iQ3ZAiHNA9QHv/LKOpc/NCfg0hnqrT3XtAO4ft9AmTjO2R2
5QidBb3XZIP0mOkA7XVrETVPxkPvEf8aaF4LUq7o6wdJJX4GBnwiijR1hlGOodDl
QltLDojP/D8Z5L9CPyDxRtXAgBRYrtAVUNOZLEHEVjMb5b1m0mfMgqF6BH4y6DGo
YICmNmiCrEPHJ4xjsuYg/Kms+6W1lvr84Az5Ccq/CMh9xp7SkKgGyyEFyncN2Njc
89VASZp6G7sBXxdKPnYYZ0fZWrjrYT7wy0N8gj3YYy4WF1wR3iOapJMwAzi410/y
D2L70wOXugcZljZYZmPau6jTyzvrTA7wQF8W3vGVoOVJVpE1lRyDN7iMgPYIHy7i
bntRsTO6XwCdb53EHvnnTF2AJIilKq4HKz8aFFtUp93FB7AHidwMBg5J1hQeM59l
QpH6IIQ/ssu+9hUm7Pvv5MizfPjNTfszYR0+59KfmkXr2pzffFzfvUfNRRwD5jUc
WbpZ+J7dlDND+NFGqUYOpuAwUhfLHTcGTuW/0ZT2u2OgnR9K+Qck1/kT0BK4var1
KJpx0DP8vMj6GISShDERJB4nJL8VJiRvEeSHB9jMPX1tUjH8wVPJ6Mss3ajtM/lp
slX80qxXs4T5qU6CHO+S
=E4/J
-END PGP SIGNATURE-
AC_DEFUN([AC_FUNC_ICONV_TRANSLIT],
[AC_CACHE_CHECK([if iconv supports //IGNORE//TRANSLIT],
ac_cv_iconv_translit, [
AC_TRY_RUN([
#include iconv.h
int main()
{
return iconv_open(ASCII//IGNORE//TRANSLIT, UTF8) == (iconv_t)(-1);
}
],
ac_cv_iconv_translit=yes,
ac_cv_iconv_translit=no,
ac_cv_iconv_translit=no)
])
if test $ac_cv_iconv_translit = yes; then
AC_DEFINE(ICONV_TRANSLIT, 1, [Define if iconv supports //IGNORE//TRANSLIT.])
fi])
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Tests passing!
Richard Levitte - VMS Whacker wrote: Things have moved on since. There's now a nvm.release-0.33 branch. One of the very first period that is not a first level separator ;-) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Tests passing!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Moschny wrote: On Thursday 01 March 2007, Lapo Luchini wrote: Richard Levitte - VMS Whacker wrote: Things have moved on since. There's now a nvm.release-0.33 branch. One of the very first period that is not a first level separator ;-) Not really: net.venge.monotone.0.25-fixes net.venge.monotone.0.25-fixes.clobber net.venge.monotone.0.25-fixes.oe-bad-certs net.venge.monotone.netsync-0.20 Argh... my heart... aches must... have branch renames... soon... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF588MAAoJELBiMTth2oCD5FYQAMVAUZmFFjEOSZDMvl1/KBDk A/Sf4cBVirhWFl1sIG8H/dCxtr2/piGl52KqQbh+oWgPn6PJa8af/Y/kOOl3z5xh XkPEfho9LHjDpAtdoyIczKQyYmLM9RaB/aQ3XkL6741RblQeH3E5t9HuZyLSewiF Y0LSzk15kqSSO7pAJL1k+Zn4NKJE2Dh5g2G5lsuRV8KwokuiiMEdnAB/hLPbexw4 DczofWZtkDoYH/OQnFHLHE8sqYa6JKKRNmMqWngbjYhvqyTlW9F4YygZpFswED8f 1Vk7WFBWMzFIpJcoDVLO+lUc4uocGC7TpR0uWQBCoztVeWQBu5ypgm/jiIQmcYk5 tnC7BRdD0XGgrU3g6up7R22kUPfDjUZwubdkSTFYyO/5lCtScdAQSaT5QbMf1knU inmaN34uT2PY9cJJq7TixGXBRxOySPj8YJvZJ/OGIQEkjCs/7z1rEU0ON2P9kkYM wUSVXJQ0pO6MBTypx/3jFc/RqKCzPX4OvwY8CI1++lH8TPLTAUHs+y9Cn0jOrojc gfLl8ntGG6SmjVgwYx/5jBzT96Dku1CQ4hg0Tszb6WZ/kKXrrmHsnqLkigcCZAmE w/suTjwtcCOI2pkmus9ZlVV4AIz+61ensjFi5bHlNr32vc6euBNP7f1ndg0S/6Qx TqVcj2T22b3P8j6TEnTD =6zag -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] forbid: a (nicer?) alternative to obliterate
Going the full way with the obliterate feature, i.e. permanently delete a file version and recursively spread this deletion like a virus upon sync, is not certainly a feature we would be comfortable with, as the would be quite a lot of issues regarding trust (oh, the remote server states I should delete this, and who is he to say that? I only trust about myself). OTOH we could probably use a strictly local forbid feature such as this: mtn forbid VERSION or, more conveniently, mtn forbid -r REVISION FILENAME that would add VERSION to a table of forbidden versions and delete it from the file content table (changing the base of the next deltas to apply on the previous not-forbidden file content). On sync, any forbidden VERSION received would be silently dropped. On checkout/update, it should not panic with a missing content but instead loudly say File 'xyz' not updated because his content was forbidden.. I also have another (debatable) use-case that is not related to legally encumbered content you are told from above you must delete: someone using monotone and his wonderful binary-content support to help deploying and updating an installed software (i.e. executables!). If one specific version of the executable has got a virus, people from the security team may well decide that is is better to entirely forbid that content, thus avoiding other people from executing them and thus infecting their system (and possibly many more executables). Once policies are here, instead of a forbidden contents table it could certainly be useful (better?) to have a sort of CRL for VERSIONs (only, instead of a certificate revocation list it would be a content removal list) signed by the very same people that have signed the policy. After all people can't (and shouldn't) be able to delete your local content (and you can do read-only backups anyway, if you want, so that's really pointless) but if you want to work on a project you should probably accept his policies, including not getting 'em in trouble because you're committing a new revision containing old forbidden content with only a whitespace change (you can do that anyway, of course, but having to accept the CRL as part of the policy itself doesn't seem too much controversial to me). What do you think? What possible problems do you foresee that I didn't think of? (please think about the base strictly local-only forbidden list and the policy-based, and thus distributed, CRL thing separately, on reply, as they are certainly two very different beasts) Lapo signature.asc Description: OpenPGP digital signature ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: forbid: a (nicer?) alternative to obliterate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Crowley wrote: Local forbid sounds to me like a good idea we can introduce right away. [...] Policy obliteration is going to be needed one day for sure, but it scares the crap out of me and I would like to wait until the policy stuff is very mature before even starting to work on the details. Yes, that's for sure (and it scares the crap out of me too), that's exactly why I specified to think about the two things separately 0=) The first seems an useful command that can't possibly bring havoc (being local), while the other was mainly speculation. And moreover if a project really needs a centralized way to forbid contents they can create an approximation of it using a script as part of their build chain (first idea that comes to my mind: it fetches a signed text file containing a list of forbidden versions, verify it (using a GPG signature on it, or even leveraging on monotone signatures themselves) and explicitly cat it to mtn forbid [EMAIL PROTECTED]). Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF4/QLAAoJELBiMTth2oCDkTkQAKZZcHtXtjAXwNq2hPcDphFq M/6aIa1inufcx5VXEkHwKVDhrA92sFNLSiIUbdU43DeiWB4mEkwPxNOsGirDRzLa 2cjcjrSAsEHVrWM4481FbG2aFTzJEt76fg4/4pmrfpBPhCIYLoNsW+hUgnWrk88w IMrFZlTucU1zcVDVnXt8nlGGatnjyCrNnYZm0roOqNCscOrKf2rMWB3NjLOqdVDs 2AmqqTfOKYnNwsxy3ppKazm5M6kFUvxfkrMZlYEITW7zD92nCHGg803jZ6mPe1bn DKI2FoDjV2Mp01owupX03oIsn0kKHjCfbWSYS+zcKFpLi2mi9OrvjhtSAdSx3WjC CqXlOrr8fM5pSTmWthQmU4j0DMr37w5ebyzpW7B6+iz6Yz+l1rO7HLPsgjTcIyCV 7fTZ+/tsel2hohxYJ/A1A4xX6mZ/xn4V1O+GSbKtaFXgznxseObAS17w22+HQws+ utA/fcION0GT0Z+wQrnfWa7Xs5fmQ1/Zp6OBfpQYWUyWyCtH44xrCetGTcsX+eBv LYS5c/wlJskqW4R98vxe1Vike79UOlH04vWwa+5+M2FexXPH9I8djWanS7u04Qd9 iMMszoEwFbwRPVNKiRvRmmLGywUHG7AJ/B9aO/C4iSrwkecjPx6zu7NXDHg8dLL6 ltb1sDfGIPTTMnlKJ2N1 =Bxns -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: forbid: a (nicer?) alternative to obliterate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Markus Schiltknecht wrote: Seems all well and good, but somehow I miss references to the upcoming Policy Branches. Is this just a user interface question, building on top of those or do you intend to add that feature no matter what happens there? The first part was an actual proposal for a new command, the second part was more of speculation/brainstorming on the possible blue-sky future. ;-) Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF4/RiAAoJELBiMTth2oCDQzYP/Rf4wOZkL0GKlqeRiMf82sJm ueGnsODm9xKfHgrU+liI5rFGfndUkC+4aUat9hSOOvTyL1S0LpYeIlf7w5zROiPB LlpIQ8Qguo1GpVkBPodtquDiOugLS9l5NA7jjjcUcMXGRg2/GY5xoNehZ9Do5V4K VTj9DqN5Gd1dzhhJZ9nCXZbLyRO9G3W2PD3QenqQ5wWedAeJ0NMc+ymu9H4xv6Yc 0t1TsIhJwqcxE93kzb5tpqpbnydRHmOdfv6bLUWE9nGnr9bpEDFC7Cd9txiNsun2 2H4l3yXSBipOFJFwAVZzxU9bTwsW9bX2eArCJ8MaGKyzLMw9bnJdtYnsoAnV0gv7 6+qAJPfB0q/vYSaL47Da+0WxjN8jBxAuS4dtLf/mgi7iYoQ9DmEjR+Y18befGcib VGkJGE1aCdxBz7s0MmmR0/ScjVt5iByE+dbAKsRvPcy88T9Cxr9cOXc4ISmL5PiV KZimasKS1NtLAlFpFqTE4Wt5jzdNvBdJ0Z4TfGZPKi1FvUzntLU6gGIz/LRIV4Ez +pUthBz8VMXiawb4+nmtEjwTt7tfqlQtZYtvp8Zn6RzlqcrLf+ZpBdRWz06goetr pfct1IAPJPCtnSvphmD6XEy5EdWq0dGs3GXtfFuRLaSYm7FUJPFf3ZLf2EfxvWrE wjC6EEOoROsICNIPyVXc =UeF5 -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Tests passing!
Patrick Georgi wrote: Replying to myself: 184 i18n_commit_messages FAIL (line 22) This fails because it relies on //IGNORE//TRANSLIT (or //IGNORE,TRANSLIT, as drepper claims - whatever): gnu iconv feature That's my nvm.lapo.i18n branch fault - I definitely have to check that in configure and use conditionally. Will do so tomorrow morning on the bus (8:15-9:00 CET) and hopefully commit it at work shortly after. Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Merging nvm.ssh-agent to mainline
Justin Patrin wrote: Compiled in msys it works fine, although I haven't run the tests on the latest and greatest (I'll do it now just to me sure). I don't have Visual Studio so I don't know if it works with that (*does* monotone compile in VC++?) There should be the raw VC++ compiler on microsoft.com for free, without needing to buy the GUI. Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Crypto and SHA-1, was Policy branches - first steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Crowley wrote: SHA-256, I think, until NIST name its successor in about five years. See: http://venge.net/mtn-wiki/FutureCryptography I could be nice if the policy could define one (or more!) hash change horizon before of which the less secure hash is accepted: this way the old history wouldn't need to be re-signed (thus losing the verifiability of the original author's signature). Of course the whole hash of the horizon's revisions could be signed (in the policy) using the better hash, to protect them. This way even a pre-image collision could generate a revision which seems to be correct under the old signature, but can be verified as invalid with the new one. While we are talking of hashes: shouldn't we maybe follow Schneier's suggestion to use double SHA-256? The speed hit shouldn't be that bad (just one more round oh hashing) and it would hinder length extension attacks. This way a single collision couldn't be (easily) used to produce infinite different collisions. Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF49jLAAoJELBiMTth2oCD0sgQAImi2MpkbfTpXBrdMXIaqGsc Eaj3icv6VpaBfIzM1TrnoN2PUEHa5RsUw+lJpe23YTezWgjq5VoWnkT9BUUjwxDU WDgq2+6Vc1GMZz8QbbqCtv0+TxgFqVy81JjxVX4iJ46Sc4jUIZ2Y10kSf8Ja12h5 lmEtWKX6Ui0AR9j0+b0980wU/FoCoU6NcSJdujdOs7RvlcAdkYZkChP5PYDEO+kt umzn1xARnx2GWChZpMQdFKtq4LDUnw8VHf3FGWpe9zdgVuVUacJOXjJLDStczLVj 1Hz2Uei6sW1LEG+dnonz+sKSoh+hHgYnxe4imSHP6Tfiz/XzlqCZfPTA/Ene7fn9 b0DfVdau5wn2Pnzk9B6HHSwvbUv7ikm+NkM+KPT8IKU5PMugwNMLFl8ppD9AFYcm dMIk8QZTDNqbzzeKvlix+P8KYLJ6mXro4bitxeRS4f1KClNn4X/eprOxIRi1Vlcx Gofz94u8zKzPjD/AecE6ah7KKg7DlDZBUjmyU+vTon/wtgn2OX+Y71sZ4/sB2JnK bN6QSNIrBTine+w91QF1ghHTZyns+HtJMlW0fUU5M2DrOOYcYnGRrDsjOY82H+QM ZAOhY6jgT40tbtGv70iQz+MSvCDR9OnKfGo+qMat+GaCw/dqjC8HN4xixAwPyR0r bMXMmE1bihlZbs/1QGj8 =1S8e -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Policy branches - first steps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Crowley wrote: Jack Lloyd wrote: DSA, algorithmically, can sign arbitrary size hashes, as long as you choose a large enough q parameter. Until recently the standardized max for q was 160 bits, FIPS 186-3 (currently in draft) allows longer q if you use a longer p (q=256 is OK with p=2048 or 3072 bits). If we want to go with it, it's a question of whether we can persuade it to accept 256-bit q. Given the fact that there is an official standard proposal for it and the assumption that q=256 shouldn't certainly be LESS SECURE than q=160, I hope and guess convincing SSH-Agent people support it shouldn't be too hard, isn't it? Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF49t/AAoJELBiMTth2oCDQUkP/1t4F/w5D4rygUUDOn32rZGb hh7jteRTm+Fui/86Gz9Y0PE4khnMl6j3B1/aCiYpoByYeaO3quJIuP+vbr5/43gd 0/Uw2+fD2qNqZU37hwD2a3h+ch5J5ETXtYGjhkAAb/+RXzKQOMu4mPfg/fb1X6Gq 4NuOimTmZ/TXLnaCKf9P57Z1/QfYx9LN/sy4JO99ub5J1TeonpfQP0k9YnElSPZL Wtx8JwfOpxgh2gVoU+2GPOVJw1qCqR5QxWB4RUBuWWwEgxvUsIcq1G3bfnyBkDrF XFCj6rlX2iQmDWW8h1lc3IkMTmvsE1NSju8PT9JD31Ke5r7O62MYHwH3peyW20VI k+9Qpxw08TPbxyInJfIwuYrkzmneJbUDb85ti6xgPllN4W74aLTlUUm2zMsoVsQ7 y9zm4EsQc0XMv5m57AFmqwOK7contntIOpRpv8ej1OYoWmPsugowZbRG/35aM5x/ IgA5XJ14SWzQkgcixvWyySw6jNO38Nhw2OusHl7A48rrr4v/tGIs4hJZAAoyNKHT awRmkCjaR78GGqYs3XUTlG3gGjv/XykfQsa84v9qqM+mYsenPIXIE0kWXD0nnLmb YeE5n3lzJPqkx4opjOO+L2mSH60zHqVHbJuqVCZlzKdis/DIQi9mXoS2XK8i3LaQ OxFZ0ukNjn3duvssN1Ix =bXt1 -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Encouraging merges?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 William Uther wrote: P.S. This is not a request for the current project I'm working on. I was thinking of using monotone with undergrads though, and they often require some constraints for their own good. Isn't the constant whining (at the very least on each commit and update) of monotone encouraging enough to try a merge? Forcing people to merge-before-sync reminds me the ugly update-before-commit of CVS times =( (the difference being they could work locally unmerged as long as they want, until they manage to merge it all up - but also has the asymmetricity of first sync'er wins just like in CVS first committer wins) Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF4W42AAoJELBiMTth2oCDcekP/0EWVfcXItiGodHxEDEanvUv e5Z4fJNlDeXmEx66AT0BpEf9xEu93QakmhwfTMscsCsDkpHuhAjd00zSEv6Cf9rB G/H1SS8C95tg//RBUyWFy53IQk6wGKmckADVppZox5luj//+tESQ7jqZstoFqNoq 7ZjH+bP+3Fjoze+4KBYCJBp/dclBcbhi1czZBVQvHyhA3PBf+BvECY6+r5WHnDJ2 5VQg0vKdW1DOePWekWbmKGgmuLhZPLzjj7KxyXH7HxbONejI6GJH84BB8Ib8rkV+ dAGF/J36UNnm8ICNE7LyRnn9tdyggH7FVVtEyKTg6xXBMVwPaipsOABjDXFAsXwP JMUg/rPT4OqJXVenlcymUbzywtHO7oZhSB6qe0tJSbZ68sHBmvoZxAAkpt5ESgi8 YPSufNn6W013Gs2rxoMqd4my2peYvyjShSv1dILWUF7fCgIja10e2TboejrTosZo an0CiMJcukT678KBaQSrBMr+MUKnH8DSEgaW3AL8k+OkhTuzt5lkO0M7DjObX5XK F6ypE+PirpLkVPwb6zLiAaj1v/gR6S91H2epBGAgRkpiaXHxivctObjuY8ty82cc aHBF5OM4HJIL7idUDnzbmjpw7IGmvXPnfM8iBSB7qIZqW/rOcYNQmkyte4af6kiD JbyZlNNaewx8uR/nKI6s =OPA+ -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] branch globs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK. I'm probably paranoid.
But I always end up sync'ing to:
{net.venge.monotone,net.venge.monotone.*}
mainly to avoid the hypotetical and currently non-existing
net.venge.monotone-sucks branch, which is of course included
by the usually suggested net.venge.monotone* (w/o a dot).
Should we need an operator that means either nothing or .something?
No, probably we don't need the complexity and I'm paranoid.. but that
each time I read the suggestion to use nvm* I just am a bit uneasy 0=)
Anyone has simpler solution to the aforementioned problem?
Lapo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIcBAEBAgAGBQJF4EaCAAoJELBiMTth2oCDCNUP+wf3v9PhD5hJINNc3T+dfZrM
9fjFrc4zg0MAj+sn4DthVcBi8PxgggxQlobudqx3TMRlSYvpbmemnUXk/jAr6lDp
q/hZX6VUSnep/g/2MgC4VmNGWZy10wXPA/gknscJ9tZoN6Ot4X+6XWPtb8yJKfXb
wp5KaB9UHw8N+ckikZ+eMkgi3xjCaVRVh7aZPgTFsQparHLqUEbUStN75EP4QfWw
Vy66yMJXYy7mMl52zG7/HXLRFG9Z/FbZ/JPYHiS0PqV2LnmJEpHcPoyKG06WHuau
aZOZgCXJ5CQ6i2DdWSazOGgsph0qtqT0rKPajsPp5sDNOFsMUT/AJdqElmWed/B9
Olx3xNxDZmBlWhLJV1EwsQRB7vES3kafVWgkfoCfhWGCpZbFUD2hd24GvDeHhMsD
yLOihC978vylF9Duh0EWlNzeKcsysHUiZxpzt6O3oTfwXCNl3eHcJT/PSCERMInm
VoyA+uQ2iCkuDrJ1EXDp5PLLrW756Eft39B8k9ssJspZvM/AkTDrZPG9TiJrVTTU
bq3ol/pY6y7BAlDTutZM1V5Y4DLoCGr4ep/EzvQZurSoXz7QpeLDnV2CuWTqHMiA
kkFpmCcVnVD4kWGSnBPIXNT8CgRc4QFo0V8S53d4Y8P+1VAqA2ld3a9M4NG88igh
vSdw9rr90PPZ3/KI1emr
=4F4A
-END PGP SIGNATURE-
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: branch globs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Evan Martin wrote: Here's an idea. Make it work like DNS: net.venge.monotone = net.venge.monotone. and also that * can match the empty string (maybe it does already?) and then net.venge.monotone.* would do the right thing. There's some resistance because this would mean that . is officially a separator... right now the system is completely free and it's up to each user to decide his own method. OTOH it would be fairly straightforward to filter tghat way (yes, * already means zero or more characters). -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF4J2MAAoJELBiMTth2oCDdQQQAJ03aOXeEJ0a1yFiat8UFNQK 2oNgUBn8wn/mR8l/NnjEnp2dSjXbkNSYYJa9A9hRxKIry2GzXfLTwBWtfsPBmZsL SgFFW5J6aR/SSXp1PqlSay3m8BcxP5G8GAdjJziB1AMZwfPTHT82B13ZzfHw7U0h +r0z8o/Ke4gdZs+dC1R909l5SxhBONHXaJLF4ZsLaR7qv5CIlyiV2fr36a7hlOkU rLb9xOQgz1rLwHINBKTBRqpA+HoHM97NoTJHyr+DPXCKXRLg9ZSYGD5JPr/flB2E cD5grivRA9jgvAFk5+mY2KGjYHJGYmZrAcH+cTPL5sq9ZytO92tE3cuJZ8pzDYSD qH4j+w2jfGU/eAcnePWVjHFCrRQ59R6gJg6vwuLOS77uxcMwRZwM8KZ/JLapomcw qw+m3XH9GXP+XFR/QGcixxM0FNs9yTqGSuo7Ho2r6a54+7fT9mq9EPamv8aEjlAf DRGkp6SE+N/n6HfXrSSVv8bT7SlJGoAUEhvyXXwpCjUAqAUH0R5t+2SIM+1De4i9 CJtC/O4UzhkFYNARKulH+CwhzFQWaZq0GIvTgJnTtK6m+rKPBX+kfJ/uTW1WoiZQ 1mQKon9k8eXDTnTVgszbQK4YavZWFPBuawDTf2RM/5cKjfTS4wcfzfuLv94ho8Is cJ/E0WW/RijG4Zg8bTeL =QK1T -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: default branch for monotone sync
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Evan Martin wrote: Am I doing something wrong here, or is this expected behavior? (In the latter case, is it desirable?) It is in fact expected (whether it is desirable or not, is debatable). The best way to go depends on your use case: a. --set-default all the branches you use, and sync everyone of them at every sync (not desirable if you have different branches accepted only on different servers) b. use a different database for each project: each database has his own defaults regarding server and branches to push/pull/sync sync does not use the workspace branch as a default because sync'ing a single branch is usually NOT what you want to: it is sometimes less efficient to do so. Example: revision 1 is on branch A revision 2 is on branch B and is a child of revision 1 if you sync server A you send revision 1 only if missing if you sync server B you send revision 2 only if missing, and revision 1 IN ANY CASE (the server is filtering on branch B and can't possibly know in advance that you're sending a branch B revision whose parent is in a different parent) OTOH if you sync server A B or sync server * the server has knowledge of branch A too, and revision 1 is not sent unnecessarily. PS: this is efficiency, not correctness: after having received it the remote server knows that revision 1 was already locally known and ignores it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF4J/vAAoJELBiMTth2oCDCTQQAIQYBTXXNgYmODiCbEgBhUYQ hX6bIYX5Wpf7b2NXPDDgAzBUH0ObEY00JM/mKwyod6hPX+8KD1aWIzQWcEBCtBWM sy1T1CtMjUqof4n3wCz+zvBL6QqCxbFaC6IuFi01zUI8ovjzf7dw6K/niaJmtrZd uCcLwzx/aeOOCXelF3albMG4nVZ5DZL2w6WXyPQnbpmNpC5xyXVmid9w8lBfA4vB T4/z0T7o/bAN71GBVhYHkEeGdGeKA5+yd3UwfM2CT8rEAtJTEcwcdwk+OPc6OyZA bhc9BUFM9rH/d5qbZozxKmeGnG/CCr+Px6DIzM17umqvEP52VnyObbNY/3K3LrXs OyBsenzfjCnQ8h35pmZswPYxKqCjIJS+Gh/wxbL9oLsPP0FQQDC8pCvtwrORKlNb di6rOS5BT0ejvVYNNp8ukERhA+3+Q/cdkMfUPfWNM+r6O3E+9aAvgaTr705JZzL0 uJzqlAoY53RtqlzwPtpt6Z1TgL2wMUwnhXwy7+qQj+DSkOkqdKIbTU8QsbIiOd5G nNQ7QtP5ByaHmtQUeKqn8G096xXfssSLuah/m2bVVJiksC/LXSviulVg7u+Dmk2W 6diKJt1uZ/EFVZsmb5RxCQooPsDFXggTzFLmyhdUP8UHlFOQvsImobVTulPcNZxm pEUQaN1s99wkgcw8nvIn =awqK -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Release?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lapo Luchini wrote: Take in account that there is a known bug using reverse (that is, from older to newer) 'log' without --no-graph, when a revision has more than 2 childs. WRONG: there is no such bug (and never was, in fact), I only thought it was not supported, but I checked and it is supported indeed. A revision with many next nodes (parents or child, depends on direction) is written this way: | | o-.-.-.-.-. |\ \ \ \ \ \ | | | | | | | | | | | | | | Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF3qu2AAoJELBiMTth2oCDsEkQAKWBW/MaIQyQRFG9VFZ1CIUu z0vJI29Ot9WyaokfQDaC+pnlqj6FtOJ1p7/p0J28MzScjxMWpLHexs/nnpQWKS8j 7RZMa6jPiF+1knHfzPF/o0Y+TfwklmyhFGJIy/zcny1KTYuJrOZahiOeCEuoblLb kM8nqH/UAXJLGQD07bDi6ziErILoXPIHBJhEcw5WJpY5OoZFFSBRlLtcrPVSeaO5 0rH2Z8X0/ER/yFXbKYxy5822h+AdrFGI/TmFvvk+KqHKO7PlHckSRnYHcUD/ffO4 wrQh8uir7GaSSQeWNGSZaHAhzSZhMX0eVGPx1glxguR8NdQuT37dHB9cqfbh3YmV gnGhluKaQoXk7FEIzx8PI6xtcNFrKLSy8HsXxU1MARwJLetAsCHisdbOibG9uYZ6 If3FnhAjRI7WbLVHN+hkr8NEi+FQRQvBrl7AABHO0KzH4L1niVT2aL85tJOBBIOE vgGQ64fZc/xKN39Muc4wFwUYkKONJA5zBMSs0qX5JCp4gCswegeTH7n+eKWxPCgK jweWaKKoX53Sj6Ld7WRRhLZ1XpoByfxJ0fN8nHxhGh2QeYWGTQLEdYIZaolOvyf2 wv4sRQvlPoQob3uLobpRAZXQOsI1OcM+cdpMb6j9Rf95KbPEVawA9sU+x5XpLcvo xRV5dhALO/kyPRejW4H9 =Rb1H -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Freeze on Windows using ssh transport
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: A third possibility is that there are issues with the talk-to-child-process code on windows, which is utterly nasty. It took ages and ages to get that code working at all, it's still very difficult to understand, and there are still intermittent failures in the test suite that no-one has managed to reliably reproduce, where it just blocks forever waiting on the child process... (our best guess so far is that it might have something to do with windows having a broken buffering model for named pipes). There is a identical (as far as this description goes) bug with rsync-over-ssh on Cygwin, that most people blame on Cygwin's spawning code: that's why I was asking which SSH was in use exactly, it would be partly a relief to know that it is Windows's fault, and not Cygwin's ;-) Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF3rynAAoJELBiMTth2oCDltQP/igcZehHFXP5vyM6unfO+Nzj LGHmo/7b660T8WizOoVPbQDbQcC4PaTMo9IAnegEA2IL64S4t/jSdtP2NLI0slZb +Ua3Ir0eaXHZwQAvWdWXC0l+OFM85IcuiBvmjVrJ9crg/5S1OGKVONPTOMN1VASz wnkduQK7IzeN8st35gq3wtThlgg1/ge6bAeb+dZ9vmHBktSPVL9XXB+Yy9p5clja iSyxYwWGNCr/OrwZnHEeIqN6iS7HM3p4zwvob1vbwJopPZeLElyahvA1igUr21LU o4fEjRtuY3plc8iRfv0MJfswXPRo0yHQlG3NvFec9to/TBLIsWagV3T898bNFFSM Z0xTZDViOEZplmqiH7Kolm2ZzMYb42EtTWgAzWh0uHCmM8Pw/UOKUWUmL408zvh2 LOluBmcV4jFPm50qKakyXyUIBULnueW8HDMMpmMm2geoajfcAmNm96NcSj89dDXn qhyuySzWHuZKaYLc1U7tI83aN/GDH7D1HT5gj7sYsQAWZCh1muZHLA6DA+mxUcmm Dr4hI+zHXVK1FSgLj+Wp30rfa6SCweFJWryuiy4Bs7zgVSZTe+ySo3YEhJlmvzAM xuj3R57pDGTfI8hK7gB+ZO3Th/YbAKsaKi8qEJzuWEdhPAb31EPMhh7asggc8WLv 7SkDrCEEgWKOKJocCqPj =Tjxx -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Status including unknown files?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: The trick is that a directory's mtime changes whenever a file is added or removed. Note for the future: that is more complicated that it seems because it depends on the specific file system. E.g. it is true on most UNIX ones and on Windows NTFS, but certainly not on FAT. And network shares could be problematic as well. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJF3tBjAAoJELBiMTth2oCDXGcP/RBDkC9C6RbMgm5BR4F+73NQ KBzIMRok/smoULRy5xfD4pvVZdTrdQf5rFlRGfQ2CH5hLoBUqxn8ECFTVkEuuPK3 194Iy01Fi6C+fMqBrucWUsfKvvZggVKlQpW4o+OxPxpiHHUMYsTLCloUzXQbeG/1 Agb48m5NNtVG3hEEkuufm6K5ClDgDsUVsJchIdPO2924cpYc18RobOLC02pS16oG 43w3IkL0F39Nq9Tb+RbB2+i9iKhi7FUFqxVBBahWZ6kvYzC5pCEMFryt0cID6gAB dQfdfd0didaV4MC2AIRHdIxMTTwz8/3ALudp/MMScetyHO7dUBb7VFwihCYZe4XT TXcJ25jQ9owekz262OTgOgTinQlmLL577hn322R/6IHI5nLlhm5tqK7R9Bi50EZ0 pmNzCcAAYrEroMTk19J80n31N/ncDdym1kMalmRW2Nv5PXBuN8K6gBzoOb7GHKzl cDThG/dMEHVdg1nOAlyfPxgUnzilBbKPLTsHQjx0vKxMCY9suUgEsG2JdPj32wwr JpF9BYQOYYb4s3AeHjUBNtExTQT7E5ApzxxOIqpJXlSO72FBbt7PmWuRzLAlQa59 rc4JUAGsYWW1Yb30mUvnNdf2SzQD//sAheBMyJxhVV7PSIyxyY/U2C+glNr75PKA St+WwHjmCv07S184DAJS =i0U1 -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Freeze on Windows using ssh transport
William Uther wrote: Having started everyone here using monotone, we're now getting freezes on windows using the ssh transport. Which SSH? Cygwin's openssh? Putty? Something else? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Release?
Richard Levitte - VMS Whacker wrote: Yep. I ended up deciding to make the release based on revision 1ce6710ef7aebc6dff09ca1bf2a54e7907fe9959, which is just before the merge where log change got merged into, eh, the line of development I was following ;-) OK, I'll make sure it will be polished and ready for the big audience in time for 0.34 ;-) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] monotone's OpenPGP trust [Was: MtnSummin+GPG?]
FYI one of the byproducts of the recent summit is also the creation of numerous trust paths between most of the present persons: 1 01234567890 .---. 0|\aa0 0 | 0 - 0x4B9C7CED Christof Petig (Wuppertal) 1| \0 0 | 1 - 0x8A89EF39 Christof Petig (work) 2|3 \ 00 | 2 - 0x5E0DEBA7 Daniel Carosone (NetBSD) 3|3 0\00 | 3 - 0xFDA270BE Derek Scherger 4| 00\ | 4 - 0xC8F252FB Lapo Luchini 5|3 000\ | 5 - 0x80E3CA8F Markus Schiltknecht 6|3 \000 | 6 - 0x1E08C1C0 Matthew Gregan 7|3 \00 | 7 - 0xF4E92C43 Nathaniel Smith 8| 0 0 0 \0 | 8 - 0x5AF9C516 Justin Patrin 9|3 000\ | 9 - 0xD61C6B98 Thomas Moschny 10|000 0\|10 - 0x797DC75F Zack Weinberg `---´ (taken from: http://tinyurl.com/2gumr7; results may be partion: only what is available on that keyserver is listed!) Dan also had the idea of creating a monotone branch to create an association from people's monotone key to their PGP key: net.venge.monotone.public-keys (you can verify that using annotate or even log) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Release?
Richard Levitte - VMS Whacker wrote: Considering there seems to be some instability with this new feature, would find it very horrible if we, for some time, transformed the feature to be opt-in (with --graph) rather than opt-out (--no-graph)? Instability as in the known bug I was talking about, or instability as in (gasp!) random crashes? In the first case, I intend to fix that soon (already have the idea and shouldn't be very difficult, only have to find the time to actually implement it), in the latter I'd definitely want to know more about it... In any case if it was for me I'd rather release without the feature than releasing 0.33 with opt-out and then 0.34 with opt-in, it's not nice to change the UI when not strictly necessary, isn't it? This, of course, if in the end we want to have it as opt-out, which AFACT was the general idea, but I don't have any strong opinion. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: summit photos
Daniel Carosone wrote: Lapo has one up (maybe temporarily?) motoko.lapo.it:4692 I did mean that to be up temporarily just for 1-2 month to be sure that each got every photo, but it could stay there for as long as I wish if it's useful. If you put one online too there will be less need, but redundancy is good. I also have one at 204.152.190.23:4692, which you should all be able to push to. This server will be permanent and will grow a name when I get around to it :) Nice =) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Execute by default?
Thomas Moschny wrote: That's why I personally would prefer the third option. An unmodified file can safely be dropped. A modified file can safely be forgotten. These are the operations that can be undone easily. No need to clobber the UI with --extra-switches. I agree that --execute is a bit unnecessary and that un unmodified file can safely be dropped, but a modified file can safely be forgotten seems false to me: in that case you forget potentially important local changes... Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: iconv diffs [Was: Why is utf8...]
Ulrich Drepper wrote: iconv -f UTF-8 -t ASCII//IGNORE,TRANSLIT And don't even think about contradicting me, I invented all this. You may we have invented that, but it doesn't work at all in the iconv 1.9.2 that's installed on my FreeBSD box :P % echo \xE3\x83\x9D | iconv -f UTF-8 -t ASCII//IGNORE,TRANSLIT iconv: conversion to ASCII//IGNORE,TRANSLIT unsupported % echo \xE3\x83\x9D | iconv -f UTF-8 -t ASCII//TRANSLIT,IGNORE iconv: conversion to ASCII//TRANSLIT,IGNORE unsupported % echo \xE3\x83\x9D | iconv -f UTF-8 -t ASCII//TRANSLIT//IGNORE iconv: conversion to ASCII//TRANSLIT//IGNORE unsupported % echo \xE3\x83\x9D | iconv -f UTF-8 -t ASCII//IGNORE//TRANSLIT (nothing: that's correct) And, on the Fedora box, it doesn't really seem to matter, IGNORE seems to be ignored anyway: % echo \xE3\x83\x9D | iconv -f UTF-8 -t ASCII//IGNORE,TRANSLIT ? % echo \xE3\x83\x9D | iconv -f UTF-8 -t ASCII//TRANSLIT,IGNORE ? % echo \xE3\x83\x9D | iconv -f UTF-8 -t ASCII//TRANSLIT ? % echo \xE3\x83\x9D | iconv -f UTF-8 -t ASCII//IGNORE iconv: illegal input sequence at position 4 Anyway, this evening I'll go and do some RTFS, which is of course the only real way to have a real answer about behavior in software :P Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] F and .str()
In the code I sometimes see: cout (F(...) % p1 %p2...).str() \n; other times just: cout F(...) % p1 %p2... \n; I guess the second form works because the formatter object has a string copy constructor or something like that (?) Does it make any difference? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Why is utf8 type _NOVERIFY, and other vocab stuff.
Nathaniel Smith wrote: (Also, there were reports that the _best_effort code didn't actually work with lots of broken iconv's found in the wild...) On Derek's super-laptop UTF8 to ASCII//IGNORE//TRANSLIT actually failed just like it was plain UTF8 to ASCII. AFAIR it was a Gentoo. I'm willing to debug it further, if someone gives me access to a system in which I can verify the failure... or, even easier, I could create a smallish program that only has a fixes UTF8 string inside itself and ask on the command line for a charset and simply call the iconv function with those 2 parameters... OK, I'll try to do that on my way home, on the bus. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Why is utf8 type _NOVERIFY, and other vocab stuff.
Zack Weinberg wrote: The //IGNORE and //TRANSLIT features are glibc / GNU libiconv specific, but I would have thought that they were available in recent Gentoo (they've been around since 2001 give or take). I thought they would be present on *most* BSD and Linux available today... Uh. I know nothing about Gentoo, but I would have thought it was in Portage, but this doesn't seem to be it at all: http://gentoo-portage.com/dev-libs/libiconv The real problem, though, is that an awful lot of non-GNUish systems have iconv implementations that are useless. I mean _useless_. They implement hardly any conversions at all. We have to have the (list of names for ASCII) - UTF8 shortcut for _correctness_, not just for speed; real live systems don't support conversion between their own locale's name for ASCII and UTF-8. *headdesk* Well, an iconv that doesn't even know how to make conversion *to* UTF8 is no good for us: we simply can't use it. An iconv that doesn't know about //IGNORE//TRANSLIT, OTOH, is good for the strict sanity conversion, but not good for the best effort print-to-the-terminal that I wired into mtn log (but other places would need that, too). I guess the solution could be to add an autoconf test for support of //IGNORE//TRANSLIT and, when not available, we can easily write a quickdirty lossy conversion from UTF8 to either Latin1 or ASCII: #define UTF8_to_Latin1(u) ((u = 256) ? '?' : (char)u) #define UTF8_to_ASCII(u) ((u = 128) ? '?' : (char)u) Or maybe we could get the transliteration table right out of iconv... It might be possible to bundle GNU libiconv, but I hesitate to recommend that because I recall its being another Haible/Drepper build system monstrosity like intl. IMHO we bundle already too much =) Many systems have an iconv(1) command line utility that may be helpful here. Uh, right, but writing a known good UTF-8 string escaped on the command line seems a bit trickier to me... no, not really. % echo \xC2\xB7 | iconv -f UTF-8 -t CP1252//IGNORE//TRANSLIT · (that is, the correct and converted U+00B7 MIDDLE DOT) % echo \xC2\xB7 | iconv -f UTF-8 -t ASCII//IGNORE//TRANSLIT . % echo \xC3\x80 | iconv -f UTF-8 -t CP1252//IGNORE//TRANSLIT À (that is, correct U+00C0 LATIN CAPITAL LETTER A WITH GRAVE) % echo \xC3\x80 | iconv -f UTF-8 -t ASCII//IGNORE//TRANSLIT `A Derek (or anyonelse with Gentoo), what do you get with these? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: landing asciik
Nathaniel Smith wrote: CIA-1 [EMAIL PROTECTED] net.venge.monotone.experiment.summit07.lapo-gab * ra49064dfd9face7387efb663a13646187be18931 / (1 cmd_ws_commit.cc): * cmd_ws_commit.cc: non working basis for asciik-enhanced status. Before you go off working on a bunch of super-totally-_extra_-awesome asciik stuff, is the super-totally-not-so-extra-awesome asciik stuff ready to land on mainline? Here you go, revision f6e078288f63ebb0ccc5bef3a56b07f1e221feb6! Uh. Right now I do remember why I didn't land it earlier: Dan reminded me just before having to run catch the plane (and in fact arrive quite early, as there was virtually no traffic) I'd have to update log examples in monotone.texi, and I never did... Well I guess I'll do that sometime soon (as in: probably tomorrow morning on the bus). In the meantime, people might want to notice that log --brief has changed to be a 2-line format and that the old log is available as log --no-graph! Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: mtn: error: sqlite error: unable to open database file on Cygwin
Ludovic Brenta wrote: I just discovered that the problem only occurs with the cygwin binary distribution of monotone. It does not occur with monotone-0.32-setup.exe from venge.net. The two have nothing in common: the one on venge.net is pure Win32 and does not use CygWin. (whether this is positive or negative depends on personal preferences: Win32 is faster, CygWin knows about symlinks and home directory and is overall more POSIXy) Also, it occurred to me that maybe the problem was in locking the database. Mhh... about the problem itself: I can't really understand what's going on. Is your database on a network drive or something? FAT or NTFS? Other infos? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Cygwin tests completed
Justin Patrin wrote: 26 importing_files_with_non-english_namesFAIL (line 24) This one should be fixable... Still failing currently. Yesterday with talked with Nathaniel and Larry about that quite a bit and kinda came to the conclusion that the only real solution is to use the wide system calls (the one whose name finishes with w). Of course we've got MANY layers between mtn and the file system, but will have to take a look someday. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Cygwin tests completed
Matthew Gregan wrote: At 2007-02-07T10:45:56-0800, Justin Patrin wrote: I've completed running the monotone test suite on cygwin (it took a *long* time) and there are 7 failures. Most of these should likely be set to expected fail on cygwin. Here's the list of failures: 26 importing_files_with_non-english_namesFAIL (line 24) This one should be fixable... Probably only needs a CHARSET=ISO8859-1 or something like that in the environment... At least, that usually solved it to me when I'm in need to add a file name that contains accents... Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] make check succeeds in cygwin [Was: monotone head builds on cygwin with no changes]
Justin Patrin wrote: I'm currently running a make check to see how well it stacks up in the unit tests. The run I did yesterday ended this way, so I guess that's great news: % tail -n 1 ~/monotone-trunk/unit_tests.log *** No errors detected Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: monotone head builds on cygwin with no changes
Bruce Stephens wrote: How can you tell if something's working if you can't run its tests? In the old way: I try it manually.. Of course I'm not quite sure it works in every little aspect, but it never disappointed me in any test I've done. Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: monotone head builds on cygwin with no changes
Olivier Andrieu wrote: you don't need any special configure option, simply use CPPFLAGS: ./configure CPPFLAGS=-I/usr/include/boost_1_33_1 btw: In fact, that's what I do in the monotone package build script. Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: first summit hackers arrived
Markus Schiltknecht wrote: After a somewhat adventurous trip from the airport to the hotel, we now realized that, back in Europe people are just about to get up again. We are all quite tired, but really looking forward to a great week! Me and Gabriele arrived February 1st, and began to visit San Francisco a bit, today we'll rent a car and take a look around the bay area too. We plan to arrive at the common hotel around Sunday afternoon, if we manage to change the booking (which I made starting from Monday). As we both volunteer to drive the vans, let us know when you are in touch with the rental guys and when/where must we meet to have our identities in the proper paper authorization place... My cell phone is listed on the wiki, btw, and from today on should be turned on, except when sleeping. (I don't know if this evening I'll have wi-fi access like I do from this SF hostel...) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: monotone head builds on cygwin with no changes
Justin Patrin wrote: Any tips on getting make check to work? I've rebuilt boost supposedly with test support but am still getting linking errors. Right now I know that the unit-test libraries are in /usr/lib so I'm trying once more... The person that is managing the cygwin package of boost seemed a bit pessimistic about the unit-test support, I kinda tried it for a bit then got fed up... but I didn't look into it much furter, as I was only interested in a working package at the time, not in developing ;-) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: monotone head builds on cygwin with no changes
Justin Patrin wrote: To monotone, at least. Just in case anyone didn't know I thought I'd say that I've built monotone from net.venge.monotone on cygwin with no changes to monotone code. This is great news for the Summit and just cool in general. Ehh, yup. Didn't you notice I create an official mtn package available from cygwin mirrors? ;-))) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: MtnSummit: Recharge Day
Markus Schiltknecht wrote: Has there been an agreement on what's supposed to happen on the recharge day? I've never been in San Francisco before and would love to see something besides the GooglePlex and my Notebook Screen ;-) I'm interested in knowing that too: me and Gabriele will be in the Bay Area since tomorrow, with the purpose of taking a 4 days long good look around... but we wouldn't want to dulpicate what we will eventually do or see on Recharge Day.. so... please let us know if there's any idea around ;-) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] nice history graphs
Taken from: http://trac.edgewall.org/ticket/1492#comment:15 What people really want (but that might be some work to get it implemented) is a gitk/hgk/bzrk like display of the history, be it for repositories (resp. branches) or single nodes. See * http://lwn.net/Articles/140350/ (gitk), * http://en.wikipedia.org/wiki/Image:Hgk.png (hgk), or * http://samba.org/~jelmer/bzr/bzrsvn-merge.png (bzrk) for examples of how it could look like. I wonder if a graph (as ViewMTN used to do) or a more tree-like view like this (which is quite close the textual one NJS proposed a while ago, AFAIR) is more close to my mind image of it... Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] MtnSummin+GPG?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Quite off-topic, but will of course every participant to the summit who wants to exchange key signatures with me and everyone else remember to carry his key name + fingerprint on a piece of paper, will evveryone? We could even put an event on BigLumber, I guess some other people (e.g. some people at Google or nearby places) could be interested too. If no ones has cons to the event on BigLumber idea, I'll do it someday tomorrow. 0=) Lapo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFvKzbAAoJELBiMTth2oCDVp8P/0Ij70w37IyoHbam/qhC3HCZ 3LNfQF2Qhr8kZfh4frxTeO02rKKNlKOHdwpRrU0qFFbqfNMqJHyv+Y9ZYxizySZG cgCnaiTxquaXrr3LXMPphK0tf5+9QoT0ay96jaYX7Ng+U4TZ4l8CJMTuLPT74yxZ gaqS27y9k5QZdxJJ0F3EmFH2T+fuH6g9N/bMsjsaNwGxLwyhxzFE5tCR1LGGhQkK C4XIKPPKTQ6iA5TpFCyB7H+TmsqEqlgLCU7VgW279L9B71jDAU9sJVlXKMsuWkM2 auLdMV+2KLgmaSSNuY0zT1NYFiHKMQYcjeol5FY9lJ6gc6B8xKu5UqPNsIJBOMJe aNzm4ahXRl74D/LADyrKJmNQ6irS/kUt6R97wQQqJuCqVAcjChJ8NpNcxGHmmN0e QfuOLz7Ni9e7+PaOncnBGWeATlqKtcHDb7Nr1reNuXfzIFSJPQpuoB2BozRSDUVa +dLvwsDVvrXvGWnoJ70gwjk9PIrmy0/wjSZrZL4ONSdybkK+pQwckFBx5IS5lIKl PW+PQnyKj6GnnEKb2IMO6UFM3lwE8jOfCeVw+M1KgJpx2wyMYiYH5BNSVPLmue6s nOUrVASD1Qcw26Sk8BAuInR+eXmOjVhE0ShXk1Q2J893UXU2PasyZxcYAkC1xBY1 mi+utAg9ANE9y8Ps0iwf =Dkn5 -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] migrate caches
I was wondering: any real reason db migrate doesn't do mtn db regenerate_caches automatically? Is there an use case where someone may want to migrate but not to regenerate caches? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] a little *-merge history
Nathaniel J. Smith wrote:
So, I've been thinking -- always dangerous -- about merging again
Ah!
I've done that dangerous thing too, and finally managed to read it all,
step by step, and finally been able if not to the extent of grokking, at
least to have a base understanding of that star-stuff (or is it
asterisk-stuff?).
For any latecomers (like me) in the mathematical theory of merges, I did
follow this path (I hope it doesn't miss too many steps):
unique-*-merge
2005-08-06 [cdv-devel] more merging stuff (bit long...)
http://article.gmane.org/gmane.comp.version-control.monotone.devel/4297
multi-*-merge
2005-08-30 improvements to *-merge
http://article.gmane.org/gmane.comp.version-control.revctrl/93
deterministic-*-merge
2007-01-12 Deterministic *-merge
http://article.gmane.org/gmane.comp.version-control.revctrl/197
Reading them in order leads to a much better understanding of it all
than, for example, reading them in another order. Or, reading only one
of them after having read a couple of chapters of A clockwork orange,
for instance. (then each user would be a droog, each merge a
SLIVAT'SYa and so on...)
[disclaimer: I choose one of the Russian translation of the word merge
totally at random, I don't have fault if I chose one that is not good
enough for merge as in revision control or even a bad word, ah!]
OK, I definitely should not write e-mail at 3am, but after all that's
the very time NJS wrote the det-{star,asterisk}-stuff too ;)
a a a
/ \ / \ / \
b* b*b* b*b* b*
/ \ / \ / \ / \ / \ / \
c* b c*c* b c*c* b c*
\ / / \ \ / \ / \ /
# / \ # # #
\ / \ / \ /
c c c
Is that lower-right diagram not a thing of beauty?
Definitely =)
Lapo
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Not storing hashes in hex
Zack Weinberg wrote: It occurred to me that we store a lot of SHA1 hashes in our databases and they're all twice as big as they need to be because they're in hex. Oh, I wanted to say it since day 0. Or, well, since I discovered that Sqlite3 has no problems with binary zeros. Or maybe I even did write about it. (I do remember messages regarding 'quote' in SQLite, of that I'm pretty sure) Anyway: I'm all for it! It may be a small an unimportant particular, but for me it's like a small itch on the side of a shoe ;-) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Deterministic *-merge
Nathaniel J. Smith wrote: It would also require some way to actually define # for text files -- this algorithm has only been written down for scalars ATM :-). Anyway, the answer to your question is that I'm not proposing anything at all change in monotone -- that's why I said at the beginning But wouldn't a new multi-content node be needed to represent the # values? Or could they be simply calculated each time from the parents themselves? (but anyway that node would have to be in the DB with some identifier and moreover probably not being extractable to disk, unless we use a clean way to have double contents? some ugly stuff like CVS' I guess? but that's ugly...) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: [summit] One week deadline for booking hotel!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel J. Smith wrote: We have a group reservation in their computer under the name Nathaniel Smith for group Monotone. These rooms are being held for us to purchase until January 20. Whoooa... 5 minutes 25 seconds of call, I hope to have got all the numerous spellings right, or at the very least the credit card number ;) mtn: exhanging reservation data mtn: last name ^ | first name ^ | conf. number V | conf. e-mail ^ mtn: 7/7 | 4/4 | 6/6| 12/12 mtn: warning, the HMAC protection was not available on that media, mtn: transferred data subject to possible corruption Confirmation number: KX9LY3 Lapo PS: I reserved only for the period of the summit as we thought to take a long nice look around the area in the first 3 days, and thus be free to sleep wherever we are at the evening or feel like to, but if there's a reason against that please tell me, I guess there's still a bit of time to change the details of the reservation, still 3 days at the deadline and so on... ;-) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFrU94AAoJELBiMTth2oCD/f4P/2YyXu9VOVg25tDGbmNwu7A1 J97M9+2VDPZmUX7yQjYcWklmBbes+gLJq4Luuakun/K0zZroDa4/6doWwXt1TNt+ SviJ/jcIoUmvW7ryaWiyHJjVkRNLG+L9+xvUImACAVfk+IUgG8DoB0TDqekEqhLa 4R3NCrdU1265KSdrXv7b3ArWGVNuoJTBLjJXX3EprGwXyoxHzUO+xIex8oIDSX8/ t1UDA+fN19+xR8j27cOyvC6GJ5r2ErJinp68/K5fYTjr7Uz3fQFv/XyPBM5xtN6T 1gyRemyrAgchBpxkuLFc54IAvU30+8UZhRrqqqQFu2MdmkRIx/HRqLb/0tjb3GzW j+NCyq4LHszT4FaQvWDcPz4RJrUUTfsfjSADyjJ3jHC0Ybb2CO/27/9Y9F3Iwx5t bkU3Wsr2j6/owD6NkxtAzFqw12gUqAOAkfua1zQnJbeTTWzp1AqGJ5ZyHMtQS8gS Ui0wugky9ZIcpTsmaWZS0ZuGjN57nzNg6htT3Rkius4U6DAlFujVU5wb+/KeXRmK imbveorEazC+fA3tRpEO/N8vIFpzMaZXMqfIoTmwSLDFly/zy7bQpVkyHI2Q2D7s YVj7Bdwhwpdq24yQSN15EXUG95MxY9iywB96FxQKIOC8e36y7nUxmUughNXuoPNV aTlu7B8fbaqIEvaBgN/o =i1jr -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Summit update -- 1 month to go!
Nathaniel J. Smith wrote: If you don't have a room to sleep in yet (has _anyone_ booked a hotel room yet?), then now is also really the time! That, I'll probably do this evening, as soon as we decide the logistics for the few days before the summit starts (anyway has suggestion what is at a reasonable distance and can't really be missed? we have 4 full days available for the trip before the summit starts). And speaking of transportation, we need 2-3 (or more) people to drive everyone back and forth from the hotel everyday, and if you can be one of these people, i.e., are: -- age 25 or older -- legal to drive in the US (IIUC if you are legal to drive at home you are probably legal to drive in the US) then you should let me know, so we can figure out the rental stuff. Me and Gabriele were thinking about renting a car anyway, in order to take a better look around the area in the first 4 days, so there would be no problem in doing this. How should we move in that direction? Will it be a centralized booking like the hotel or not? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: MtnSummit Hotels
Markus Schiltknecht wrote: I'm still looking for a room mate for the MtnSummit. Did you already arrange hotels, Thomas? Anybody else wanting to share a room from around 2nd to 14th February? Me and Gabriele must still call the hotel and reserve it (and the time period is roughly the same), though this doesn't necessarily interest you if the rooms are 2-places-only... (it wasn't very clear if 3 was more like 3 places room or 2 places room fitter for 3, but I guess a good use of the old phone medium can solve that and more doubts ^_^) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: nvm.experiment.pcre - boost::regex replacement
Zack Weinberg wrote: we know distributors want us to move toward using unbundled libraries, and PCRE is nice and stable, so this should not pose us any problems. with FreeBSD devel/monotone port maintainer hat Hey dude, what about that external LUA could be usable after all because we can overwrite system.os() with a null value anyway stuff? We gotta reduce that tarball size, we got to. And bzip2 rules in that way too. Yay. /with silly tone that was not very much like a maintainer Just kiddin' ;-) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: [PATCH] _MTN/log pre-specified magic line quickie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lapo Luchini wrote: It's like it does use heavily UNIXy things like fork, I guess... Rephrase as: IT'S NOT like 'diff' does rely heavily on things like fork()... - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFiMslAAoJELBiMTth2oCDfRYP/14/aa8++f/QdDUekcyPF03R TDgrRKU0PYBJBUSebnjVXvE0Ce3W0MeVPcob6+7tpRyHgcW1XbwYfO3u0L0nZFXJ 8vMXCWfPDuSMkP7x+RWbtuPZq9OzMe0Yo9tG6w8aMxH31ifyTyGdZH5X41r6PaMu 1yOsWvmxL1jScMv3QlI2zfskfmLoZ4usqjsRLklTzslGbNZY6z0HkEnYHZ+SwPLP m9Rsmo4/EfyElDRRXSJDBRq3HBCU7WUaMeM/XysNiA5OO1kR/nAmdqrFRKlA7FWH 4Bnsw6dzxbD+eQx7dQc35Nw7ztOLbNF6m5NR+YgPmFjtzd38JjQhmvIb5oU7LvWs glMjnCkzQUHPvZQecHsoixb2Cy6xwcStvOlh3vosdflAYyqAHpx8QMJesXK2nGkg 3lpt58pbDg9iDBz6KwZu36kZeSZe2XsZjH86/ZawwTXN55Rg/lXDVyNfNDOdc5wr jgkfnFc/2YbnjLt/La+gGDAh+r6oOZr9kECF13L86g04+VGzCnl8P6eMSYkKzFkl eVygZoT6QNDZOxDL8A9ZzemMWyeIynAX0VpMojz/O92HLBj5j6dhfv1iKZ8t5Nhc SdpjiROwRaRPUwa6Sm5lCZgWvsFT03tAXbxV91FbyeLYaPDfxoT551g8d/NFoI89 wOEj7CnlhVJgSrCAJYC0 =8wqn -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: European MTN Summit
Thomas Keller wrote: I'm definitely for a), and as the MtnSummit page states I'd favorite some date in mid February. The question where we should meet could be answered quickly with Germany! since many of us come from there, but personally, I'd also like to go a little to the South, like Italy (Lapo?), since the weather should be a bit better there =) As long as the travelling part of this summit does not exceed 250 Euro I'm fine. PS: Please say something, *anything* if you're interested in this, don't be quiet =) If it will be in Germany, well, I'll think about it: as little as it could cost, after going to MtnSummit.us it would be a bit too much (on available free time as well as on bank account) to go to MtnSummit.de in the same month ;-) If some of you want to see a bit of Italy during the summit, I could certainly help with logistics (and probably partecipate). I live in Milano (big, busy city with lots of services) but I was born in Firenze, which art-wise is much more attractive, if a bit smaller. Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: [ANNOUNCE] North America Mtn Summit: Feb. 5-11 2007, Mountain View
Nathaniel Smith wrote: Okay, time to just go for it. I hereby declare that Mtn Summit 2007, North American edition, will be held February 5-11 in Mountain View. Yay!!! I can finally finalize my travel logistics ;-) Unfortunately the he 410 EUR Delta flight MXP-SFO seems to be no more (now at 587 EUR price tag), new lowest price is with US Airways at 517 EUR (and that price seems to be pretty much constant with +-2 days departure/arrival and both SFO and SJC), so I was thinking to actually depart on friday-saturday (and thus arrive a couple of days in advance) and return on monday, trying to take a look at San Francisco itself (never been on the west coast before). Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: line endings as project policy
Nuno Lucas wrote: On 11/22/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: If we use an internal line ending standard, we should consider the possibility of using the standard newline character NEL, Next Line, 0x85, unicode U+0085. You are forgetting I can (and actually I am) versioning C files with text comments using some code page other than ASCII (in my case IBM-860, because it's a port from a MS-DOS program, and the original programmer was Portuguese). Not really, because in UTF-8 all chars bigger than U+007F are (at least) two bytes long: U+0085 encodes as \xC2\x85, while \x85 is not valid UTF-8 (only multi-byte chars can use the high bit of the byte). In fact using NEL would be nice because it has the correct meaning (while \n at least in principle means next line, same column), but it opens a whole new can of worms: in we use that text files MUST be converted to some uniform Unicode format (I'd say UTF-8). Which means that we MUST know the origin format on checkin and use iconv(). And which means that on checkout there may well be cases when the charset chosen by the user is simply not capable to encode the repository content; which supposedly means either you error out and ruin the life of that developer or you lose some data on the next commit. Don't mix character encoding problems with the end-of-line issue. They are very different beasts. I do agree, let's do line-endings first (as a sould be done thing for the user), and think about charset conversion only later, any SURELY as a optional part. (e.g.: if you define the charset attribute it will get converted to the internal format, but nothing will be done in any other case, or by default) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Dates for Mtn Summit (read now if you're interested in coming!)
Markus Schiltknecht wrote: Wow! Where did you get those prices? And what source (ehm.. departing airport) are you flying from? Milano, most probably from Malpensa (MXP) airport. I don't remember right now, but 95% of the foreign flights are from there. Last I've checked it was 800 EUR for me (Berlin - San Francisco) A quick search on http://www.travelstoremaker.com/cgit/porch?agentid=onthefly returns this example flight at 520 EUR: Delta Airlines TXL 2007-02-02 12:10 - JFK 2007-02-02 15:10 JFK 2007-02-02 17:28 - SFO 2007-02-02 21:50 Return: Air France (on the behalf of Delta) SFO 2007-02-12 15:35 - CDG 2007-02-13 11:35 CDG 2007-02-13 13:15 - TXL 2007-02-13 15:00 Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Dates for Mtn Summit (read now if you're interested in coming!)
Nathaniel Smith wrote: And, we need to pick a date. If you are at all interested, even a little, in attending, then please go to the wiki page and use the ingenious code posted there to indicate what dates are probably possible for you! Though I (think I) have the proper C++ skills I didn't dive into Monotone code very much yet, but I definitely would like to, and face-to-face contact with other developers sounds like the best way to do it, and sounds fun too. I still have to ask my boss for a week off work, but that shouldn't be a very big problem (I hope). My main constraint about it is to define the logistics and get the AIRPLANE TICKET in time enough to have a fair price for it. E.g. right now it would be around 410 EUR for San Francisco and 530 EUR for San Jose (we're speaking of that Mountain View some 50Km from S.Fr. and some 30Km from S.Jose, is that so? there are some other 5 or 6 cities with the same name...), but that is likely to increase quite a bit if booked near the flight date. So, please, everyone interested just update the wiki page with your preferred dates ;-) (or if you don't feel like using the wiki just send me a private e-mail and I'll update the page in your stead) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] mtn automate tcp
I was thinking... wouldn't a automate tcp be useful? I mean something that just accepts TCP connections and then talks the automate stdio protocol: having an always-on server listening on 127.0.0.1:something could be very nice e.g. from PHP access, when it would be difficult to maintain an open automate stdio available from all workers. Or there is some problem against that I cannot see right now? Lapo PS: this could be easily done using tcpserver but that would accept only one connection at a time, for file-locking problems, isn't that so? ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: mtn automate tcp
Thomas Keller wrote: Ulf Ochsenfahrt schrieb: 1. Security Hrm... maybe its not that good idea... I was thinking about 127.0.0.1 anyway, but there's the multiuser problem of course (thought it would not be an issue in the use-case I have a dedicated web server and I want to access monotone from some web-app). What about file sockets? They do have permissions like usual files, I suppose? Anyway even an authentication like all or nothing could be sufficient, as having access to the file itself gives the same kind of all-or-nothing authentication. 5. Multiple Access You'd need to figure out some way to handle the locking issues you get with multiple concurrent access. There is absolutely no concurrency in stdio today and I doubt it is useful to allow such things when stdio works on a single db in the backend since their access would need to be streamlined anyways. So if an action is running, the service would probably need to give some busy signal back to the calling request. Or wait in queue for a few seconds and only then giving the busy signal, but that wouldn't be a very big problem. Do read-only commands (e.g. automate get_*) block the DB totally as well? Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: mtn automate tcp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Queiroz wrote: I'm the author of a web interface for monotone written in Lua, and got myself thinking that, as I already have monotone running all the time to serve monotone clients, it could as well receive fastCGI requests and process them. Why not a fully-fledged WSDL-based web service, then? From PHP it owuld eb a breeze to use 0=) But in fact any of those methods could allow to do a quick front-end converter for any other of them =) - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFXgYUAAoJELBiMTth2oCDABMP/0HtAXBXImIOWEA1pTGvAXKb 1Y7HBtrwYOHaOhgchA1Zwck34XdjYq7zzyEfWzlkeGdyLNLwRkM1X+vhYoQZE0iu S1DggpwiPaOT2o+vdddqmLkkrDp2Bx0IOfhVyDFBlaj6xobrTNg69NNTboGo72+q 7f1jLVW4HAN4xD079mf6EnrqYaWO1A+19Hodd0O3128mOGqMqmtzEW/+uCVzrdue GHTzQfio3oR0pfg8Cn8NJkYMZpDuah9KDRZbpY39wXabNps2EExwMQlrkOBDZ1YU n3UUA3P3xTmbT1r/YIaDV4CB0qgeSNjGNF7EfirNUolWvMA6S24d/K2jEHuZtuqX cWAjUlL1kNcWEA/BGq/JxJs5pMUrF1byyND8u9WXocEovy3mJKx6VRYF/wg0+nvX 8Fac8/VDu6HHA2zoNBhryn/yaYYxw9VPIgx4Tfi0oRQZE8LvRU7r++2tSNFfFTQ0 QScYvKHOmiJl8m7bYB9ILxrjIwUnkkqOknI6168Ut+v4j7SrOg/C5Htkv+vvYnW8 9evx0FV9mZWZPkWJeixC1qpYYQ3KpUsp73h8rKqP1Kes83zzMZe8jUCWoYC1jxN+ mRogsOSiLTAh52u8e3mi9iLKSbNt3vqZ/8euz7tLi2mgDqr/qy6nUMGzslP+Bg1B qMZpNR3EDx3AMo4MgX96 =EaVg -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: cvs_import benchmark
Lapo Luchini lapo at lapo.it writes: Lapo Luchini wrote: So... 6% improvement between 0.26 and 0.30, and a 100% worsening from 0.30 and yesterday's trunk! 0_0 Not having a working callgrind under FreeBSD nor Cygwin, I'll guess I will continue some kind of binary search in the remaining range to pinpoint the exact problematic commit. But well... trying it again (this time on FreeBSD) I noticed that it was actually solved in 0.31... good to know! % for n in results3/*/stats.csv; do echo $n; cat $n; done results3/cvsimp-mtn30-time/stats.csv cvs_import-system-time,0.32,0.28,0.35 cvs_import-user-time,49.2,48.69,49.04 cvs_import-wall-time,94.42,51.55,51.22 results3/cvsimp-mtn30b-time/stats.csv cvs_import-system-time,0.42,0.43,0.36 cvs_import-user-time,181.86,182.43,187.37 cvs_import-wall-time,186.34,187.47,191.86 results3/cvsimp-mtn31-time/stats.csv cvs_import-system-time,0.37,0.34,0.37 cvs_import-user-time,48.92,47.98,47.79 cvs_import-wall-time,51.8,51.04,51.28 I still wonder why the problem was there in the first place, though (the changelog in that range REALLY seemed innocuous). -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: cvs_import benchmark
Lapo Luchini lapo at lapo.it writes: But well... trying it again (this time on FreeBSD) I noticed that it was actually solved in 0.31... good to know! % for n in results3/*/stats.csv; do echo $n; cat $n; done results3/cvsimp-mtn30-time/stats.csv cvs_import-system-time,0.32,0.28,0.35 cvs_import-user-time,49.2,48.69,49.04 cvs_import-wall-time,94.42,51.55,51.22 results3/cvsimp-mtn31-time/stats.csv cvs_import-system-time,0.37,0.34,0.37 cvs_import-user-time,48.92,47.98,47.79 cvs_import-wall-time,51.8,51.04,51.28 In fact, the system-time increased a bit but the new wall-time is kinda IMPRESSIVE =) -- Lapo Luchini lapo at lapo.it (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Google providing partial sponsorship for summit
Nathaniel Smith wrote: I guess this is now official enough to announce: Google (specifically OSPO, the group behind code.google.com) has offered to let us host MtnSummit.us at their Mtn View headquarters, feed us, and defray lodging costs (which may mean provide free hotel rooms, and at the very least means use their purchasing power to get us good hotel rates). I pasted this on the wiki page, I guess it's not a problem (the mailing list as public as the wiki anyway). -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: FreeBSD's requirements for its future VCS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian May wrote: I can think of two evil reasons: * somebody committed data without permission and copyright owner is jumping up and down threatening legal action if it isn't removed immediately. AFAIK, this is the case they're concerned with. So I suspect removing the trail my be required, but this is going to be evil, and potentially break past revisions - it might just about be better to start a new archive from scratch. Also, what happens if only one line of one file is under dispute? Or if the dispute is resolved and the copyright owner agrees the code can stay after it has already been obliterated? I guess the two main approaches may be: forbid a revision or forbid a specific (file) version. The first has the problem that it breaks the chain on hashes from the root of the tree up to the current latest revision, but has no problems in having the same content later on, if agreed upon. The second forbids a file content altogether, which is kinda sensible (is that very content which is not yours, not the fact that it is in revision xyz together with other thousand files) and could let every revision logic work as expected, except checkout and update would extract the full revision except file XYZ, because its content is forbidden. If the content is to be had AGAIN... (but I'd consider this even more rare than having to forbit it in the first place!) I guess either: a. it is a source file: changing a single char in the file (e.h.: whitespace) can solve the problem b. it is a binary file that must be exactly so: I guess an epoch is to be used as last resource... - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFWr7AAAoJELBiMTth2oCDzxoP/03pN3JsBKIadEgnKMQwuCmR aC2RM9s6B4zexq+s4BXRNIW0Ioravvx8Vq90vOefaUSuVNDVWPt01TwdyErp5ma2 kks0oLQWpi64K05Njfw64CE6Apcxpzvj8RpnErGEqmpeQabsJV3ZQ7U+63yPpFeq SfNpjxwxcG4d6kX2OPMOy6JMVLbU7WOyA1EeblEfcGNzM4smXag7FM5qPz6Dn0qO YOeYEptU8hYMgx/dM+ktzZ41vhOjktd2GMIi/EeTINRAxICe7dV/sisvONvltdG9 8qnyi/0hRvcB/l1ZcAA8o4bktrp+BGaaosRO9O19DKaUbgL++P720i4InbWNmXrc w9IkMnEIinL7utDIZIlektseFETGxWa7CMjDTOk0tprZLLeI4zRkoicE2m9ymMz/ B+cBgCwuppteEhsQ5feUN2UuFGyUSMFYX8wL5jO9Pw9VM9j8WZcW2eTw9D31NCMf eCpyf+YSaFBPlP6LPnWQxfOazpgqD2zEuFwwRSBz6bdO9LZWv3PT85p8RebzaawZ mj242cVEDcFlrgZvLVls64tjJq5e/ABg2yKdj/C0F804Bs4UUO/cdzD4KcdauTmc ocgIqIatGYBc259xzW/Xfukj+t4KvOyPY2iHNZQTSE1HIgb8gt+pGnZZpYBs9jyR LKZj1iRMgiG/eV16WkIS =Nj8c -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: bug report: windows monotone can't check out files with parentheses in the name
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Keller wrote: c) at least bail out with some nicer error message (and not with almost certainly a bug in monotone), like The file xyz couldn't be checked out on your system because it contains characters in its name which are invalid on this platform. Consider renaming the file first. or something like that. IMHO the concept the file is in the revision but can't be checked out is the best: that way you could even do a rename and then able to extract it even if you were not in the first place... - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFWr8+AAoJELBiMTth2oCDFXkP/RJ3JZ4XOb0iDMAPPA5IfWJj ir3Km85NI5v1s55U0ntUvsqqaLdX5covKbA2MjDTMgC74gPFGB1te8gNnD2fR0e/ 6sdMScB1FAXih5L9rXu8N3HCh5JYx925fhpXC4GMUpbWeA/MrrZh0I5OoeM+A21G moNuliu/Ti+VPjxxn24d140nwVUeywn1y7yD6sf9GCjmiQU51Xs0v9dut/8VslUu dgmikt9owtV3NYaUuoI7dJ2QMYRIrxk9iDiXr7gfORIKhf8zH+gQePfPBELQp8HC ziBYv06N9WO2YiUW3Ak8dc3jaE35ZjakOoe5xzyb/5LeqvoDm8jZR7IqBky80g8u 3D+mth5iQd1JCUKatQORJRyAuCCguxk2IQR28ymHNfVnlxXgB/u3jWsoUfsapYPh Gf2rOyKaaGhGL5d0h5kZ0jIabFtjBRSzeuUZPXlsNRdX/Lp74x8rcxxQLRgMZP2a FPFaosunSBecnc3uTCeS1khiLPAtdWpBjmtQatXDgcLp+e7n/K8uNN10Sh68ccdh 9eesSzkLmV1iCJlcPnSAR778Munznrwf2ZJEGksq5P6JPXJ2bVuUmN0DpFczCHvK b8GJYorIsK/L4OEWaTMgtLID+GE97I1Gvy+S51wfUDY1EIOkjff0L3mEA0F0UKBY nuC36byg6eS4P70iHAHm =H8TA -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Fwd: Re: FreeBSD's requirements for its future VCS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bruce Stephens wrote: I'm not sure how you'd get rid of a file. I guess you have to take the revision that added it, commit another one that doesn't add it, then rebase all its descendents? What about adding a forbidden_content (id, reason, certificate) table to the DB and: a. delete the files with version id from the file table b. delete the delta which produces that version from the delta table c. adjust the delta of the following version to skip the deleted one d. spread this table like every other This would of course add an invariant to be kept valid: the version listed as forbidden_content must be deleted (and deltas adjusted) from the DB. In case the users extract the revision with contains file version id the file would not be found (of course), but the usual hey, I've lost something, PANIC! message should become a warning more like the file 'id' was not created because its content was forbidden. I guess this would be as far as a distributed system can get regarding the obliterate feature (or the punch holes features as someone describes it). Does that sounds like a sound solution? (yes, it was a joke) As FreeBSD seems to consider it a very valuable feature (and it's obvious to everyone that it is my dream-in-a-pocket that monotone could be selected as the successor of CVS+Perfoce by them, though it is quite improbable), it could be my first serious code contribution... - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFVlDfAAoJELBiMTth2oCDzcgP/iv0Sl1GG8+/t7u7ZqI0GRPp fL3ZLywGcIcArLCZblmqYZLDnMCik1T66SJPzBhy9ULWnM3mrjIKDh3XzlkQhC95 tdLmXmw1MjteEEoAwWncntgXnZP7uPiqGWISZJbrPytCuWOdyuryLsFbEKZ2zIld OgFnObaX/qFhPH8jbHoQz4P2pGeC9ptHiGd/xkoOqVjXv0IyuVQPcTXOf/nN73/j dyvhvxB8HJzkJJVwzOaNMJAAfu+INgoB2lPLfXVLzcWtEaLHjJjRX2ct15hr1n4w 4qyK9DwS4zzrIDr5v+52rOXSBWFGYD5xrLtEeWsuTknuv+b4TJWtbswaJA0/wnNt eIjow1+SVfx32+5qGbGx0bsJhZhG/POSpikeBIijQ0sh4mSQT5IILaWZdccCNH07 dpL2Hk5HRdOvwVYno9PmUYvBBZbZU7zNrIdhpNWxUQM90cM63RKLjl0oAwBhAY2p n19FqWBr7maCo03P75FjBFHDSDkaUfPeiIyUmii+FEtrtOPx05kVr/aVvFsT3IYU XWrhJt+joVvo7DYyyDUrZNXmaCHMk3NKSaWiHVjE3kuSShcxoewOOfymTIsX2c2O wgOyzFtAqee0ir/xY++eTcSaUCjP8zvj8cHDjenCRZCL5WDNY1oYeiz8G1OuA8cW e9EZgM8GKWhc3wT8Uakt =bPXR -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] [FreeBSD Wiki] new requiremnent: VCSDatabaseRecovery
New page: =Description == We want to be able to recover from database corruptiopnss of any kind. I'd say we may well be proud of monotone in that regard, isn't it so? I'm thinking to comment like this, please correct/expand it if you will =) PS: there's the EuroBSDCon in progress! I'll try and talk about MTN this evening at the dinner and tomorrow at the convention itself ;-) --- Monotone authors are quite paranoid regarding correctness of the storage, and never in the (recent?) past a bug managed to actually delete important information. When in the (far?) past users had a database form some reason unusable (at the very least, there's disk corruption) they went so far as releasing a specific version for the recovery of that specific database. The database itself is SQLite, so everyone can easily see its content and be assured about its soundness. -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: HOWTO: benchmarking monotone (was Re: memory exhausted error for 'mtn list status' command)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: As an example, let's look at the InitialPull benchmark. I know no Python, I have no idea what a requirement is, I wonder why this as to be declared as a first parameter (linke in a language born when OOP meanth nothing 0_o???), but thanks to this clear tutorial I managed anyway to do first real code contribution: the CVSImport benchmark ;-) I'll time-test it on a variety of platforms and examples, for now I can only say that, on Cygwin, mtn-0.30 is consistently 6% faster at cvs_import than mtn-0.26 was 0=) - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFLWeaAAoJELBiMTth2oCDFPsQAMN8AQRjnRF7yu1QLufESj18 I//MqSBGtJQFBVhKbOKSPF6sb7xAQ304PXSnRMHxftt6qiyxwgbX2eb7AeHLiCoT c1LdDUNMxLC1JwBHUuvbE48M1scuSqEFf4RPv4QNR9nCX55WMwCfMwrlvAWz15K6 MdpQua6QgOXsG9VZPUqspKoXZASRYWUes2mTgIhv1QfIbmqIqS8zitxObfskshNv DURUs55fDnZzeiIFLPZrfr6OPSDuLXcIBdvwfReeE403sSW6f5Gb3G4HIhqtZAkY 9BTEZctp4kSDCQLUTOH1GbCG/T7EdYyd2rCTf3sh+Otp2yMeAoJ+ZF+vRQdrAj6G KqFXJ/yr7HG42b2kkp+aqXtKUAeQdupn+rdr3QODcwgruCyUT8JG1l+O00NqOlQv qxHsPNlVwdevbKQBEkZxmCMelTFCMJlm4mZVjqA9Vx1lh+bWLHSuErwR34sBeMs3 N2wDx7EpTMEsKaz6ZCdUwW4ytEnZv0L6hL5G3Z3kJ4clP2bEDsHcO4pJgnj3ZG0U s0GrQdA1OWH4inl/Kd7z7MxnRUBQT0167MKpf6pfPTtIBOfCTMCsmvTaeakz/kpY e/G9ik0VT42L9+o3BW78GUKTwJSM+o0ybYlS2eI9l6SGq8iFqwV9eX9fIwHLCXRk 4NUB37DIvTliYqLmBscN =MiiO -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] [stone in the pond] OpenPGP signatures?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 No no, I'm not talking about importing raw RSA data or the such. I was just thinking: would it be useful (at least to someone) to support OpenPGP signature to something just like a project do (sometimes =P) feel useful to sign tarballs? And, if the anwser is positive, what? My personal brainstorming: (some things partially true, some debatable, some plain false... that's the very idea of brainstorming afterall...) It could be useful because... a. it delegates the problem of trust to an existing web of trust b. many people know it already and feel confident in its signatures c. people could check the signature manually It could be used to sign... a. manifests, because they directly contain the hashes of every file contained in the project (and if you trust SHA1 you trust SHA1, and if you don't... then you can't use PGP web of trust anyway!) b. revisions, because they contain the hash of the manifest, are smaller, and the signature could even be stored in a cert In fact I think a openpgp cert containing the raw detached signature would probably be the best, and it could be done entirely with a small script or wrapper. The easiest way could be to directly but the armor in the cert, but that would be unnecessarily large and bulky... can a cert contain binary value? As a SQLite3 field I know it does, but as a command line parameter of mtn cert I guess it does not. Just to be fair: It would NOT be useful or be straight disruptive because: a. it instills the doubt that mtn own signatures are less worthy b. it adds much data but pretty much nothing, security-wise, in the DB c. the very idea of needing an external and existing trust is debatable - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFK+N5AAoJELBiMTth2oCDFzQQAJhOIoN5uJcw8Hv86dX3p2pF RL0KTloEE/QuuIwL2LfnM4nt/iELVlAJtpu6bXuuRB59fSjaBvXjCAFttk0XRmYC 4VieoiYn+/LSAvj87ADHm6vPnHqbPV6eC94O/1s/6Basya4xDbCrp1p87/2szRH9 3C0jfJvvDBtksI2iLEi1sg8+cphjKUFsRm7Ztfn5V19rs219isa95ZcfM2B22ihb HlBqtbGAbYCLBIxxSyotovNymJhYgn3JjYEPGx09ybzVD7ViJJYKfR6U1/T/gfzO eRBDNm9uIWPkAqsBLmZ+bLhecPI/Fb+A1DnquiwqHMS3q8+cK4f6CWLC1FMeAXjA XjwHMzFaddvpNhUc3GmecUxeL0YjXr2alzk3mT6vDUmCmJF3iS5T+KK9RB2pIu7P NnMqfzWvOzCAoh3kqc1eDvWfSWR0q/hVzbXethKuppD3z4ZUaP2NfL7E+kjSUdid CsnFcW3Qo9JAILzNv1qIqYyErVQwkACcobHnq9Yxy7k/2LhUuA0P+TGsvkvBoVU+ eCzk8R1AmH/aR0cFBrmLSj0GehXFJU+MhRKqiX0oOCywFtiMpaSZ4B881izS5Mbw UzBxkrrVIxuN0+Bzejskp9EZd28mBnD+0tUukcGc8Z5ervz4sVzhOs3fLTnuNZi7 LILDzxMonKKAmb4gGfUj =0V3U -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] committing .pot and .po files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there any consensus whether a change that changes the .pot file should commit also the auto-updated (and, thus, full of fuzzies) .po files or not? As a translator I personally prefer to import the .pot file manually from inside poEdit, but other may prefer to find it already done (espacially if they use software that do not update from .pot files) - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFKO6sAAoJELBiMTth2oCDlgQP/2jfRasQj874ge5ll17vWtcE GDY/y/7x+ZwYbD7JEJ8RBF9GyrzqmEVAb4WBcMRnLfvIcWSG6rlBQth3grZRyq1X Ml88x0GORgh9cuuoAtHZn+cMGnYuH/eoHEVhJ4bq9+EPuGc0RdnbmTJJCvPAvX3J LNii8LOEXOcySuYfRedtHS3U6+x8ITmbo6Hr7Jo7VEq+RiR08uKsOhRLkEJ4KeaO CYGONvJZfe+bsd5i+nTyHXxREeUOqSzmP9eWiFACi2+91Z1/vJRS2bOeN5fuPDG3 NFoA6Qbhabpxo1PS8zdGPNrTMfuRJ/s61rDTwDttNlPzlOMNlBt6mJF2zVR0GT16 11IM/VRt/UNnKasz5eEdo96NI1SWotw+nq7VHvinEv6uBJLHagocbgqDe1Yk0fdu UugqFPqPuGMmdda1hyOk7RKpudQHjtqDAgdLcMrJV8BnbEYTQhS2HCuC9qtUpTng blBQiJ9nt5hB/BRno6rDJGHf7fR40QufCsaCinOEUOiDtcYzmOL4Fq0IOEu5OH3e VbmlgOwnAhEjxMSxrZrgUNr7dx18SZUcXLqcFIB8Y0KBPNJ6UPR/iBv/1gPDYNhr l4ppi7lRS3tezV0XiC+8GbqoDQ5nQg6+sH5hYPLl1ZUEgaEfaqU0WUHPhVhslsGh 4URAYP2MqVH2djqdIvMZ =mLwK -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: invariant 'I(!next.empty())' importing FreeBSD full sources
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lapo Luchini wrote: We'll see in 3 days and a half... 0=) Import not finished yet... but the previous error were around revision number 25k, and I am now around revision number 31k, so I guess it's actually solved. For the curious: 'ps' reports: 42209 p1 RN+ 6219:18,44 mtn-trunk -d org.freebsd.src.mtn ...that should be: 4 days 7 hours 39 mins 18,44 secs I found a BSDCan (Canadian BSD meeting) slide stating that FreeBSD's src (once imported to Mercurial, I presume) contains 122238 changesets. http://www.keltia.net/freebsd ...but it also states only 24 branches are used, while my cvs_import run had detected 403 while importing versions (the first part of the import). - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFJ+9ZAAoJELBiMTth2oCDg1gP/2ZMaI0CslkuNEFrrY7ghPx3 3gtcKUOhSszdmPy49YLQVeZCc6D7Ok4aLHr0DDtM5o1OG1qeNARKxe5jXM4G/br6 E9GWwkZLoXPq0iotTmSTBldOxqYiVhkiD9fBCfDkzuIiU0s34GUAx13j9ix2GdVj N9NqBPPZ4KlyNxh1+WRP/CDduTGAxzpHlCBe29pvNrWiJsRPw/LCqAlPRcreimfo 8HQNQOY9qCsmZbe+LWK/Xz9n2GmusdJvar/jbeGKOTHK4eD2Ce6nXxSXO5wksG/h hVhN3DTv5TYStw5FpkrQkKqvikcoyYEP3yyNrgHriY/opW9wtZiRiGaWlvR6GSvR K27rJ0YbPbN2ov9TqmyHjakyyWpFp2GKaqvwqTQm0v/TfBB9U+IBZooYATalggDy fDOVI2tSk2WHqoqMpn+SUGdrHEFmywMTIKXfcFNpYDs9s4Y1ZCAUSiBOPve4smFl S5i9L929BSGVAHuG8dsc3uxxPAqMhH1U2eE/Z07Oaqp7kSgBcV5NFiebHhyHmX5B +r/TevZSzLYBSk0n/c5tsEwjBLJn/SZ5WOZ5/LQ7i/2JFqoct28hoW0lbNLi4J0Q a1RyM++v0/wIWpvxefNw0ZVpCeQOlPKM6kdTdxzvaovU4eK2zKlSkUTB1N/YGQid QUgTUKp9kgmrN23Uj+m1 =oTBd -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: invariant 'I(!next.empty())' importing FreeBSD full sources
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lapo Luchini wrote: Lapo Luchini wrote: We'll see in 3 days and a half... 0=) Import not finished yet... but the previous error were around revision number 25k, and I am now around revision number 31k, so I guess it's actually solved. Whoops! Forget that: it seems I erroneously used a long-ago-compiled revision instead of latest trunk... re-updating compiling it... tomorrow I'll re-launch the 'cvs_import'. - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFKFA4AAoJELBiMTth2oCDI68QAJKEiOdkJeLlNAmX9c05ycUj 1pDk7v7UwIi9yEr1SPHfYOJJdimeEwSX5wqUVE+SaXhnspdlMAm/N8zCNJ9xqKVj 7P6mP7DUCu1FS8Y8CY02sPcSoRuHAPGHtWcoQh/DhPlePEqAvt/PVAiRE9cuPOpn P7KwCmDcFcIUaEjm3NHWRuEQ7F4SNO8QKxO5D3EUCbT/qRP7kwGzFsuWa0YEmA7I 1S1dDaNH5rFK68UiHvIxkGX3SYF4QNS6J6FzHD43Jmyt0Y+8RWe0DIv4iaB4oMEt +HrB6acD7tTN3GGL3cyoXHkj4fvGTyxElFE1Rk9FEOd81JOblcGfoVn+2f8R774I jp1vuoc/2DTtjYrhQ+EQwot5h0lUQpgVjIsOnB+YJ5qudHFC9koQ0yidji7FJcZo LZF798Rvnlu9ITNzLiKmMyPcYhtSMow+Ky3z2q7TDKZ2E6EvUij54FxEFNB9yKYt cWGvafEgmrswNbZKJ0+zeDq4kImXyshtDFwhfODv5UTGj1DQ1E806PAbXHZaPSq0 WMsgEEfoc9A5fdf/kMr00qRev0u4jalFz/GKvgLVhD9oafAuVEbdvipQUweNVDX4 /Q2bbp0HSGor2EDw/24AgZFQCVw5Ec6OHoCjWDlF+4HfQL4Wb9uWkL1TP8DvYeM5 ik5eUJP+8iSJhLp4CB/z =z/Wz -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: FreeBSD's requirements for its future VCS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Carosone wrote: I've made a start, creating an EvaluationFeatures top-level page that should index all the other FeatureFoo pages, a FeatureTemplate page and a half-dozen or so (so far) FeatureFoo pages. Whoo, you work fast, I couldn't definitely keep that pace ;-) (either that or you got lotsa free time :P) Good news is I just had the editing bit on FreeBSD's wiki and am linking and copying some of your text there, so that FreeBSD people can notice it better =) - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFJX4YAAoJELBiMTth2oCDu+0P/2KoZEobbQ8N9jvvzWk38oj3 F69F06fI5LmiLovZJEKAVmH5lDsfs+kQQbrJtmHLBcVor9UbHnaRjHsWURK9ooEu nStEF/hB9WH4FkB39M3AU7HAjHZ39pabpohjVvc87/7h9e1UzdBKTrml1t/g07ZD /UB91/TpUN7+Wb7TykVJKhoMLId0U8c86zlkWBKCRMVsrFVQULFECBXcH3yN3N4K C3lSQorlEmC169jx8aiMrptIVyX8gC3f2ObV00jSrFvDW4qR6V7wuAvzLxiisPyG fK4tmt4s+F5TD46oWL6LXVcKwwhKI0cqS+IKlUtYau6ypE0kSXxTBmm0FhCG+K52 LbeQmkLWI1MC16hp5gHYjebvwxPv0Sp6JWCAoSw58g7XCu2SpnURuqSl5sbKlnpX V3HzY27HWGGre1GxZ4Zrf015oBHCU0yAzt2izmHq36/I8R+kH3gegt6LE+p78COI npHJgIT2yZegaAcJ206KRCT5wZux7pPRQLfejCbqreQcEk7UI6X3moNSPoNdL4jn MSXfbEcP7W5vai4N7VpuaeCxZlCXtQqC6OCktFVqW/mgernvGDCVRyUcFqc/z8OL lsf/AO3P2qdl3c5ZO/LIBFqvx+MfxIP/yrymo1hGkQvf/xIFbMceS4vhK3I+24t8 6o7HHdFsF3jR57izxgmW =CX5d -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: FreeBSD's requirements for its future VCS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Carosone wrote: I'm not sure what the best way to proceed from here is, or whether someone else has made further progress on monotone-specific answers. Please respond if you're working on this so we can collaborate. I can see that we might: 1- start (set of) a monotone wiki page(s) describing our capabilities, with reference to the FreeBSD pages (and perhaps also to other similar comparison pages elsewhere..) 2- start some monotone pages with answers similar to the ones they have for hg, etc. 3- draft an email response adressing each point in turn. I think I'll make a start at turning this email into #1, please chip in if you can. #2 has the slight problem that FreeBSD's wiki is still in test and, thus, only editable by authorized accounts, but while we elaborate on the descriptions I'm working to have my account enabled or, at the very least, I will ask to some committer ot insert it himself. A page on monotone's wiki addressing the very same problem list (and, maybe, other found elsewhere) could certainly help, in the meantime, and possibly be copied as #2 or #3 in the future. I am definitely willing to help in it, but as I wrote in my mail, I'm not sure about all of the problems and some help will be needed =) - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFI1MdAAoJELBiMTth2oCDS90P/0xGXj9LRvsS+QwHIxJorpnc uRfzk2EEDHsptABa7v28oimwWH6ZGD4TCH4rtv0HusOXtSDewnHdlwcWYrKIg4Wm tb0xLeeC3o96vBOvUiAPN/+cWAqVS8A/l+QnOss5myhA4W+ieZqc4VWkTHkfu3+K 5TxXrCxQlOP58vVPojJeKB2o4Aa46XshORsX6YE0K9NjaP6f9GfJIwZ/eBgqnN2n Oz2RXgN4b84fTTafyRwRXJXSgsad3oHoFdYock/kOOZeKK6y6qUx1bOh9yZaEzZj CQzvdVjL3iHPUColZNaEkqs11kkXqyvrLdUWkonBeyJi54kHgpYqO/dhOfqlxWEf o8K1+bkRZwbNEJPl82N2Ea+2nwDPOr1m3DYNHMx6XHw0GlW6hCytB3ANi6kzdVq3 8JspUT+Hi1Sp2dtyBlXz7+NRcFvumDN4mqvvMzKQcDh2QJVjOmE/qDNRxrxWg/j3 t6AdphSMZcq63iqMOFTrgUW+VFlLtUEWJsWOOrvNP0i+7I6ial/RTyP6jK9xoyeh ZsPq3LGhsiLZM1cuaUDbsC4j4aA4P1i74Lh+foU243wWUZUic58V/OS3tXx7v8d4 Iud++h45hM39ww9GAR3bstutqeCnhtXR0mkA30K8pwCnm96DIxspPBDx9LBN0AI5 OxXtxYrXqebVSXgiCSBw =E47w -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] invariant 'I(!next.empty())' importing FreeBSD full sources
Daniel Carosone wrote: On Sun, Oct 01, 2006 at 03:54:39PM +0200, Lapo Luchini wrote: mtn: fatal: std::logic_error: graph.cc:72: invariante 'I(!next.empty())' violato This ought to be fixed in mainline, with the change in revision a:njs/d:2006-09-22T07:01:26 - please try it and confirm! We'll see in 3 days and a half... 0=) (it's a Celeron 2.5 GHz, I'd try on my Athlon 4200+ but that runs Windows and Cygwin version seems to be slower anyway... btw: I should really benchmark and, if possible, fix it... someday) -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Java JDK is changing VCS too
It seems the process of open-sourcing Java JDK is leading Sun people to choose a new VCS as well. The choice seems to be going towards Mercurial, as past experience of OpenSolaris (also Sun) chose to use in april 2006. They don't seem to have definitely decided yet, though. Mark Reinhold’s Other Blog http://blogs.sun.com/mr/entry/openjdk_scm Anyone to write some analysis about the issue mtn vs Hg, pro and cons? 0=) I know little about Hg, what I do know is that mtn today is vastly better than mtn in April ;-) (well, April means just after switching to rosters, I guess evaluators may have been pretty much scared of by the very fact..?) Lapo ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] FreeBSD's requirements for its future VCS
http://wikitest.freebsd.org/VersionControl This page (and the linked ones) details the features that FreeBSD requires (or would like to have) in its chosen successor of CVS. It would be neat to be a candidate ;-) Or, at the very least, it could be a list of interesting use cases... -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: FreeBSD's requirements for its future VCS
Lapo Luchini wrote: http://wikitest.freebsd.org/VersionControl My personal analysis of monotone vs wanted features (very rough): VCSFeatureCVSImport: Ability to import entire current CVS repository, including history our cvs_import would almost suffice, branch reconstruction would be a plus; NEEDED: find in what revision a file of a specific CVS version is imported into VCSFeatureVendorBranches: Support tracking vendor sources (bind, gcc, ...), import/map existing branches. we should have this already (it the vendor branch gets updated a propagate progapages all the changes to child branches, is that so?) VCSFeatureAtomicCommit: Atomic commits to get real changesets we definitely got that, we're ACID, and Atomic is just the first letter... VCSFeatureBranch: Easy cheap branches (and history-aware merging) and tags to enable parallel lines of development we got that VCSFeatureObliterate: Obliterate functionality, to remove complete content and history from the repository in the event of import errors, policy decisions to remove content, etc kill_* commands can do that, but a local file sync is then needed to remove unused file content (a command to clean in the background while the server is active would be nice: afterall it could be read-only while scanning it all, locking the file for a few moments at the end, just to DELETE the extra rows) VCSFeatureFast: Fast system for common operations we have to work on it, with a repository as big as FreeBSD wuold be (I managed to import the kernel in a 500MB database; full import still running after 48h) VCSFeatureACL: Access control: the ability to constrain developers to operating in specific areas of the tree, implement branch-based policy restrictions, as well as to enforce policy such as tagging of commits for developers working outside their normal areas. Implementing these via hooks would not be a regression from what we currently do in CVS. I guess this is a work in progress with the new policy tree stuff, isn't it? VCSFeatureMerging: Automated or mechanically assisted merging we should comply with it already VCSFeatureCVSExport: Ability to keep and distribute a reference tree, knowing that it should also be exported to CVS this lacks, and wouldn't be easy given the single-line of CVS branches, but something could be discussed on the very wiki page regarding it, I guess (judging from what Hg and Git people say there, a commit on hook would probably be sufficient) VCSFeatureRename: Ability to rename files within directories without losing history we defintiely got that VCSFeatureSign: Ability to digitally sign revisions or repositories to avoid file corruption and to detect unwanted modifications well, that's not a feature we support, it's the MAIN feature VCSFeatureOffline: Ability to work offline -- like on a plane -- without requiring too much work: not only being able to list differences but also to commit yup, that's easy! VCSFeatureDollarFreeBSD: Provide a mechanism to allow end users to easily see the version of the source code they were built from. Currently implemented with $FreeBSD$ tags in the repo. this would be tricky... I guess VCSFeatureLogTemplates: The repo as a whole must support a log message template. Support for different templates for different paths would be useful. this should be doable with hooks, isn't that? VCSFeatureLogReview: Log messages should be reviewed to ensure they contain the correct information. For example, Approved by: re during code freezes/slushes this is almost there: a certificate could be used, with the pro that the approved would also digitally sign the info (though I wonder if would be easy to append it to the log message, if needed?) VCSFeatureMirroring: It must be possible to mirror the repository to remote sites. that's the very idea of distributed, we got that ;) VCSFeatureGoodRepositoryFormat: The VCS's repository should be stable, relatively safe during crashes, and small enough for developers to keep copies. we got that since quite a few versions, I'd say, with no real upgrade hassle after 0.26 VCSFeatureWebInterface: There should be a way to browse the repository from a web browser, review changes, and so on. viewcvs.cgi + CVS export is unlikely to be a long term solution. I'd say: either work on ViewMTN quite a bit or finish MonoTrac is needed VCSFeatureCommitMail: E-mail messages to one or more addresses should be generated when a change is committed. Format of e-mail may change (e.g., doc committer committing to src tree) easy with hooks VCSFeatureTinderbox: The VCS must provide mechanisms for the tinderbox to hook in to it. (tinderbox is the auto-building system) an update hook should suffice VCSFeatureBaseSystem: How is the VCS going to integrate in to the base system? zlib, iconv, gettext, boost: that would mandate to have it as a port and not in the base system (mainly for boost's size and complexity
[Monotone-devel] Re: po/ChangeLog
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Levitte - VMS Whacker wrote: In message [EMAIL PROTECTED] on Fri, 22 Sep 2006 18:14:53 -0700, Nathaniel Smith [EMAIL PROTECTED] said: njs What if we just say translation updates don't need a ChangeLog entry? I would love that. OK, in the meantime I made revision 30f099d35c1a70af1c52ce8aeebb0037d66ae1e8 without a ChangeLog entry... but if this gets official we may as well (only for consistency sake) remove the old ones. In that case I volunteer to do it ;-) Lapo - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFFS5RAAoJELBiMTth2oCDTFUQAMZTDU68Czm7kmuR3i40CfKk h2p2fm7xK8PzVQIx2PxHRoRMvzmXCaMcqzrS52QT4MJ9IkP00edQzAF7C7yrSa74 x2Dlzd1RpjGmMQ0LYcsI66fa8uHo6jHIaQxy2Jsb1X20GPJAbE6ElLFZsCXBjYWK rrke90jLZvlxvWOpe6T2rByqVTBNZRxTZoA9Cr6FC2Lnre/2IAOIWv9qHWrXEfpa GtDJv0rBbRl1qOcQ7vOGWf7rMpBwPeCN2uumJwJfBu235gLQf8Gab5XhRz5BwPOp zxllSAsJt+DovYvThJ/eJqG9zvM+f0k/MhtsOFLM0FyZiCZ2JRhUFxB+noXMTarr D3WrHqIwCrpppVsfl+9jCubgU97b2mFu4P5wECo7f57papQF2m/fv5tHsHvy+Mqw on1Mg0hITYk8QDMV1mq1V/MGKdQb9tszFGA2tGzTXsV+Zl0tBHB/PSgpltyBAj/z pgGOnY9eauAJ/MEYujJr40T+0jMx6HUidq+EQwqeCkmgIpO1h2PvONS79rp1bIGo ftPsMgnPflD2+zqyyE+K1G+zSA9IvTcCjRX0xXu/IuDo8d1jlRBEwukmdAa199HP 1xgGGBqfJKHOsSB9F/mtHLdwgPBmG3xUKYKB8YhMbnFV61Ua7khWMK/ikbX3ubXt k0a9X8p0YmFF2RiQzlMl =G8HW -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] FreeBSD port patches
The FreeBSD port devel/monotone needs the following patches, would they
probably be a problem on others systems, or can I simply apply then to
the trunk and push to venge.net?
I guess the common problem is that Linux by default have some gettext
calls even if now using gettext, or something like that?
--- monotone.cc.origSun Sep 17 11:56:38 2006
+++ monotone.cc Sat Sep 23 18:42:05 2006
@@ -188,8 +188,10 @@
if (!init)
{
setlocale(LC_ALL, );
+#ifdef ENABLE_NLS
bindtextdomain(PACKAGE, LOCALEDIR);
textdomain(PACKAGE);
+#endif
init = 1;
}
}
--- configure.orig Sun Sep 17 21:28:11 2006
+++ configure Sat Sep 23 18:38:33 2006
@@ -10827,7 +10827,7 @@
#ifdef __cplusplus
C
#endif
-const char *_nl_expand_alias ();
+const char *_nl_expand_alias (int);
int
main ()
{
--- Makefile.in.origSun Sep 17 11:58:18 2006
+++ Makefile.in Sat Sep 23 18:38:33 2006
@@ -1960,13 +1960,13 @@
unix/$(DEPDIR)/$(am__dirstamp)
mtn$(EXEEXT): $(mtn_OBJECTS) $(mtn_DEPENDENCIES)
@rm -f mtn$(EXEEXT)
- $(CXXLINK) $(mtn_LDFLAGS) $(mtn_OBJECTS) $(mtn_LDADD) $(LIBS)
+ $(CXXLINK) $(mtn_LDFLAGS) $(mtn_OBJECTS) $(mtn_LDADD) $(LIBS)
$(LIBINTL) $(LIBICONV)
tester$(EXEEXT): $(tester_OBJECTS) $(tester_DEPENDENCIES)
@rm -f tester$(EXEEXT)
- $(CXXLINK) $(tester_LDFLAGS) $(tester_OBJECTS) $(tester_LDADD)
$(LIBS)
+ $(CXXLINK) $(tester_LDFLAGS) $(tester_OBJECTS) $(tester_LDADD)
$(LIBS) $(LIBINTL) $(LIBICONV)
unit_tests$(EXEEXT): $(unit_tests_OBJECTS) $(unit_tests_DEPENDENCIES)
@rm -f unit_tests$(EXEEXT)
- $(CXXLINK) $(unit_tests_LDFLAGS) $(unit_tests_OBJECTS)
$(unit_tests_LDADD) $(LIBS)
+ $(CXXLINK) $(unit_tests_LDFLAGS) $(unit_tests_OBJECTS)
$(unit_tests_LDADD) $(LIBS) $(LIBINTL) $(LIBICONV)
contrib/$(am__dirstamp):
@$(mkdir_p) contrib
@: contrib/$(am__dirstamp)
@@ -1977,7 +1977,7 @@
contrib/$(DEPDIR)/$(am__dirstamp)
usher$(EXEEXT): $(usher_OBJECTS) $(usher_DEPENDENCIES)
@rm -f usher$(EXEEXT)
- $(CXXLINK) $(usher_LDFLAGS) $(usher_OBJECTS) $(usher_LDADD) $(LIBS)
+ $(CXXLINK) $(usher_LDFLAGS) $(usher_OBJECTS) $(usher_LDADD)
$(LIBS) $(LIBINTL) $(LIBICONV)
mostlyclean-compile:
-rm -f *.$(OBJEXT)
--
Lapo Luchini
[EMAIL PROTECTED] (OpenPGP X.509)
www.lapo.it (Jabber, ICQ, MSN)
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: po/ChangeLog
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Keller wrote: Hrm... out of interest, what is this supposed to contain other than fixed this string, translated that string, aso...? In other words: Who cares? In fact I always wondered if all my ChangeLog entries (all except 2 of them are Updated and translaetd a bit more (XX missing)) were really necessary/useful... - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFFGkcAAoJELBiMTth2oCDjScP/3/7LU7pvhGqJcGx6UjaMAp6 bAdlwhZabSBHy7TnQaQuJ0bJZU9si15WyLd1P2VpDLiAS+TnecgsFj8kJ+AQpXKx t4r4n+83d0NyJZpWAymQLS/b6pibgXLYTkuSK+H8UBgG+EklPSIbyHRH5zPecqmC SBWl1cZaRoq6swvfQY1vfqyls4YVe/F/E0qfyWDcQWIgh7+VOLpkMOdk4kHOZWhK 4zbXhzYYXfIw7M7pT1q6aodm8bFrKil7XUkJ0mTlyzi4a0DzMehPAIXdz1aFzU16 T+jkDkvLf9DU5kFtb/mo66J8PwfAgbNep74opy+bc3lfm1+9UWSLRrKdzd3C6sXk YFHyd8ccedStiPWUbrhTj+p1LgKDUJU2vFD9GBCBS1r5tU02igMQ/SCwDXQreBJ6 6rgE0D4Yn8pUP3Z3W0bK33qmKjl4I2do8tG7ghuC3BbG2cG2lwz/pftDPQXKCzrm JpdzFDMacIQwPKt1eZkvYp8JgIFQzE4fgGOMNVN6YGaWhkcwgH9RUE+nKIlWGTKN xbrZy6KZZQydTCokxpwSiFSRzKs82zSnIYyJsBNdGP4xfiNFKf+/Eq4s5jcLQta8 4STQ3vYe8iXUDkZPDMREEft6JvZVqmk8eqRLha+a1f1yvSAFk0chAeZGOurQ5Y3Z n7VfqTxlieh32NHn/7Xw =Klef -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: pointer arithmetics in C++
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: If that's really what you want, you need something like x1 ^ x2 ^ x3 ^ reinterpret_castint(my_pointer); (Or perhaps multiplication would be better, or something, hash functions are not that easy to design.) In fact if x1 and x2 are likely to change by 1 it would be quite easy to have the case (x1+1 ^ x2+1 = x1 ^ x2) when the hash is a collision (if x1 and x2 had a 0 lower bit) or similar cases. If speed is not a real concern, it really would be better something like: x1*p1 + x2*p2 + x3*p3 where p1,p2,p3 are some big different primes. (and me not being a cryptographer I guess it would have other problems anyway, but at least it wouldn't be weak to such frequently-happening use cases ^_^) - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFDa+aAAoJELBiMTth2oCDERkP/jN3t+U0r5kIPlqp0QIp+jKk ZOnzhqbBgB8w7zHVFNLXvbUx5w5sqq4dNn4t9VINan09QZXsqGBvLpotgFKTNnKE g82Dtm0Qn4aok+yht4eFoGgI/8OWAfvT79ToI3RkIf0XGH6SuQBg277voSoP0uGd dPLU4oKhau7aNpRxQvBObeZkpbO6ka2EU1bgs8j7PfdCXIdlZg9ANVbPXgv9x74A 9vAWCEn/fwcrBqlAB4qcrBVA5zv8s4mWwFDYPODlrDKdb3yEICMZnrtsjNyR8fhk FXRFq6UW82iJC3/qBg8brX6fn2K5zzaRqJz3foV8zieasgPPFY3MTe3dCHBADb/R AfQ1U4kR7n4euJFv9SggdjIhiuoTFaOdYR3cDwtMspBx+VWU7og3ONn4SzuAnRJv 2Elun5cOygJYxOyGJ8lJlG9lrSTjP80blwt5dE51+SyCFAerEP+4442V5PiLIvXC o6BX/mmQjiyg+3k54sqNNy7kupjaDIwmtED0TLfu+b7xCFzUYsFA84erVQpYKACx jL/FI6i9Fo9U0wNFjciJYqGd6gPMSZB8Gcroc/e4SOhpv0qyiV3Q2mNlnCvDrGcc r5YHUH/oFXqbJ91WxEwdBPjGFbJnEg36MuqVFTftFvDMkfSFRq0169V3zGJ6LCzW 75+u4AEQ4ZbxWuagD4Wm =LsRQ -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: cvs import
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nathaniel Smith wrote: On Wed, Sep 13, 2006 at 04:42:01PM -0700, Keith Packard wrote: However, this means that parsecvs must hold the entire tree state in memory, which turned out to be its downfall with large repositories. Worked great for all of X.org, not so good with Mozilla. Does anyone know how big Mozilla (or other humonguous repos, like KDE) are, in terms of number of files? A few numbers for repositories I had lying around: Linux kernel -- ~21,000 gcc -- ~42,000 NetBSD src repo -- ~100,000 uClinux distro -- ~110,000 FreeBSD's src CVSROOT: % find . -type f | wc -l 62501 % du -hxs . 1,8G. - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJFCkzEAAoJELBiMTth2oCDE78P/A5o69tRQa9LbmBTIcrqJhBz 52/0TgdErZ3gjYTbUHQMO08BmZAscw51eJfOYgTkVmvof8KeCXUp5gTT53tTN9NJ 9NKr/LjIjtgQ/JkJDLE050lBz/BIZrgYd86X90quXzDoSvikhBviLxEhetGUtVUz 6iT/3P0dGDoPNXD6plsW4sbk6PgOus9CDImehprNXxO3UjX2WebpmOThiU9EQjzK 5IF4fhc956qOwvlGJwPUWt92dZrpSLW5TuisQEg4KLTjLYYZSLWrY3ZSfblP/h1W twVB30ykRAXdNN5EscG0B/M4jFD0YlAuDSvA0YqwVkF2GeLRi1wOVhD1EPnc4PV6 yZ7OnfhYMrk5jAOEBk+QH0Hnb9X4bdvqu2SlgDH/RB5QVePgpvec1LtYt1zJ8KPl icOo2jWnbvYW0/6eWTxUJu++FK2cb08bUeH7p/P01JUcNKF09jv2i1ou8ZVOdzrj CKb4ZpUXr3pnwqXPevZIFoSWFdbp7BvwHofuwjxTa4hhzjRXAj/+Mmzxm29PO04E W9TYDh17gXVvU+1lePbBq/5O44BqnkXhMU44l+HUFbQzsl1fSb2VyA8/1KdlT6pV p/g/57+hQqzFxr1jMYXziUBvT16UC1CgTdRCyjyRRWtqIC2dXpKTAdG2r8Ijo2qh WFd3IVMz6YJCKMeOMSLy =QcdU -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: [Poll] Intermediate Results
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: Intermediate Results after seven votes (including my own vote): 1. monotone-vcs.org: 17 2. mtn-vcs.org: 15 3. mtnvcs.org: 10 4. monotone.ca: 10 5. monotone-scm.org: 8 6. monoto.ne: 5 (if available and not too expensive =) 7. mtn.ca:4 (if available / buyable) 8. monotone-the-scm.org: 3 9. monotone.net: 3 (if available / buyable) 10. mtn-scm.org: 3 11. mtnscm.org:2 12. monotone-the-vcs.org: 2 I'll let the poll open for another few days, lets see where we come out... Thomas. 1. monoto.ne 2. monotone.net (WHOIS: Status: Locked) 3. monotone-vcs.org 4. monotone.it (I could help registering it as an Italian domain) 5. monotone.ca - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJE+W3LAAoJELBiMTth2oCDfQMP/14+9F3i7ez2Aosv7Yl2Vorr RLqN6I8K9oAFXu+GpySXGpQ6mmMv4eujaGeIkahYZnFW4Os5UJprWkJYUel6tuUH mm9okDuswBZl0Kr0axz8C9EnB4k27ZRL4hJJqfi8OjjEVaam6/mDH6DJnnOHDS/p rxgdP3XmmyNxe0YZyozF+pjF9js/kmq/ZU6Tj9dF5tfyL8u70fKeUcJuXMJm3i+n rSRfZmiYQIfQS9A/nWdXzrWX+Kjm5HcTrk11UOweh2E+woczAVFzv0f07Zeu0UeG RBwpStUNvL6FLBFTse0AfAUNLvEIcjRyWJoXnlkTFp4P6WyxpWtD1qMPeT5ELRty N7I0YwfOET8+eOZGd0GiqriF0NQ+AlrrFm29FGVh92YJq7maChSfWQJogHlUwZ+U DOj/Qy397ieMmRRFpsQlS7RgQQZ+7pIl1t0nm2QHStVySiwa9AfEcZBkXSDtgKI+ YCKpuwgDeydl0F4ynPWChXIfp5pMLNbG8hJgwul8X14jS6Doft7HBJjAmWkKojou NNOsYBhbySQYgWj/ABciDj9ffB99IEIMQZ/kjgUnOPehbT1fLZhzvtDDdl38iker tBF6/xMrpxQJGLkZtHgNv0P3ISHxk2Ixw/z27WzywBuL4CewvAczZ62m/U8RWJKa tXE+DUcX4/WH59jSt4pK =8J3V -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: [Poll] Intermediate Results
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Graydon Hoare wrote: Anyways, I wonder how much everyone here really feels it's an important thing to do overall. Is venge.net/monotone (or say, mtn.venge.net) unacceptable? I would prefer mtn.venge.net to venge.net/monotone/ for various reasons including the ability to have subdomains and the such. Other than that I don't feel any strong urges to change domain, but a 2nd level domain would be somewhat cooler anyway. I propose (and am wililng to register) monotone.it over monotone.ca, or ca has got some reasons I can't discern by myself? (I mean as a pronounceable word, as a location it certainly is somewhat representative of the creator's and some of the developers place in the world) Overall .net would be the best 1st level domain, being distributed and all. But as far as I ounderstoo that would be a bit complicated. - -- Lapo Luchini [EMAIL PROTECTED] (OpenPGP X.509) www.lapo.it (Jabber, ICQ, MSN) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJE+XBVAAoJELBiMTth2oCDmMEP/jAHsWeQl3pHa3fRSxFwhP3E VLrfkAJXUxfmjF/n924q9PMcPRXNg8/HdZLNoPqX27OmzLSJxwGj+A2Y6lg+6tOX yGI9NP9W/JBwmh5i1Gk9k7xSH23FP+UseVVDvJfDVTUpDbit3YhH/HDuSiJ9zXYw 6h9lcGOBAqGM9JRGdXOcEa5x2uzY+uYMBBMA5XCsAikxw9dMxzT4bm+tmhJP0YUk qiLez6VlUGW2eZPNrOJee3zmz1mIlOiGHu9SKLWoW50QbDCO18VdPO8V1MouWsty O8qoxsEUDxz/5GUv6YyDCYneZu8TN8yOqF9y9Id+kx7JXjPKrp8SYO6fr38kVNDX YiDOYxuwiiI7tu8SE7Wh3kQY4vb1wIjAEHT0PBHi9x1TobwcrqP3kfJk97Xogtxh +YGpasD6vZH0nGXjrNmo6SFBGfeHB+4ILZiLzGlOJMkYA0N/L3RJL5YTTlBMF4/j k28kyJGxpu1yklJA/8LAI7HRuOP6KsYA7YmtAQv7q4vTwihuRoYUYno4gCNpKSYZ u5sNKcDsYPDHX+AHH3AGMlAZgYWm7c7EvI/jgaIZar/w23IqVnXTWPLhPVI/ekbE qSwqVQrGAFcqjAe4lDS0OwYi6k+ezetMERnjtV30+4v9b3kpKqQ3IqgQITQsdAEd xtXtgprVmMncB1xiqSUn =hmyy -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Re: Comments on mass_set?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Dickinson wrote: (Wouldn't that be better spelled as: $@ $TMPFILE? My shell is a bit rusty.) shift doesn't affect $@ that I can see (I did try that first). It does, in fact: % cat p.sh #!/bin/sh echo $1 shift echo $@ % ./p.sh 1 2 3 4 1 2 3 4 (tried both with Cygwin's bash and FreeBSD's real sh) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQIcBAEBAgAGBQJE8XlvAAoJELBiMTth2oCDU3wP/0YwzHBq5FWsP94xLCLg04RX PbWmcwWDLVS6J5dQWncMpzBJXj8HZZCRa3Vpe1TUwVbB/eUWtvUN4b5MYmrsSoJL ZXQiMVbhQouQV/Bx2jCLd6Ke+knGLsst8r7ds8fV/Ra6wQ2xUPDBzIs+AnOaB4X3 3wSl74iijW5iqyacuE7zbVlj7NhFxoqD+ReT9Xe6sZu33PsEwADXo8xKVr/X2zcx zZAYZJrISzKdoJ1fwcXqtRJ4GGT9vVIc7GoOafDoRQ2NtcRS67cSbe/9RptQe0vx r47ZfGGMk5mtgwfgTpsjA1htB5XqMS6iiN1Effq5bD1s/MjhBITUPUIXYPp37Ght lrvH5mDj5ECX8NxbROQCfMn86ITE1EtZRylE1kSPCR8Yjws7czWO/x8BmCislmzC fjJTK0p2SdH8g1z0tY0xLa87rGrg5J39WfzfvusDcdoO/7m3ij4DDArAOXZuWGYz OmAtMDkG0PEmgY1hVHjHCL1xUo9DKIsCUdOwjgQiJhZ+c3me/obMxF1WRlSlOFgi SyyGPnntDzein9xmcVG//+uN7yB1wQ9ptgCMcjNXjOwr+ngHUCE87/w4rLvovDh9 dQ+2QFGKrD0l6z2hdpM1Dq+89XD33hHEAz//B1hXP5Itllf58ubLdMXRV0ABwJ5H YxQKT/KVsC802lNugT0z =nCnw -END PGP SIGNATURE- ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
