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 prob
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:
# m
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 this
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 commo
-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 S
