[Monotone-devel] Re: RFC/preview: automate interface for cvssync

2006-07-26 Thread Koen Kooi
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christof Petig schreef: I would love to get some feedback on the code since it is intended to get mainline. Syncing with different RCSs (svn,git) should get easier using this automate interface, too. Could this be used to setup up a read-only

Re: [Monotone-devel] Re: RFC/preview: automate interface for cvssync

2006-07-26 Thread Christof Petig
Koen Kooi schrieb: Could this be used to setup up a read-only SVN/CVS mirror for an existing monotone project? yes and no ... you can not map monotone's meshed ancestry onto a linear path. So you can only export a linear subgraph of each branch. Multiple heads within one branch are only common

[Monotone-devel] automate inventory (mtn-0.28) shows added files as unpatched

2006-07-26 Thread Daniel THOMPSON
Hi Folks Recently upgraded to and started using in earnest a post-rosters version of monotone (0.28). Everything is going pretty well but it appears that the behavior of 'automate inventory' has changed since the last version I used (0.25) and this has causes knock on problems with clients of

[Monotone-devel] memory exhausted error for 'mtn list status' command

2006-07-26 Thread Drakie Awita
Hi, I've been a happy mtn user for a while, and the upgrade to v0.27 is ok except for one problem: if I have some large amount of un-versioned files/sub-directories (thousands of them) under my versioned project tree, then 'mtn list unknow' command errors out with memory exhausted message: #

Re: [Monotone-devel] memory exhausted error for 'mtn list status' command

2006-07-26 Thread Drakie Awita
Forgot to mention that I do have a '.mtn-ignore' file in my project root dir; its content is: ^contrib/oss\.boost\.release(/.*)*$ HTH, --- Drakie On 7/26/06, Drakie Awita [EMAIL PROTECTED] wrote: Hi, I've been a happy mtn user for a while, and the upgrade to v0.27 is ok except for one