From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Monotone issues
Date: Mon, 04 Feb 2008 09:58:42 +0100 [thread overview]
Message-ID: <47A6D3C2.10304@kernelconcepts.de> (raw)
In-Reply-To: <20080203210353.438dffaf@cimmeria>
Hi,
Graeme Gregory schrieb:
> Sounds like it is time for our regular re-assessment of the use
> of monotone. Maybe we should start another round of testing other
> SCM systems again. I know your not the only person seeing mtn start
> to creak.
I agree... I have never been a friend of monotone but got used to it. But it
reminds you that it is still not ready for complex projects. Just to mention the
pain that updates are not atomic operations and problems during an update end up
in the pain of a broken repository.
Another major problem is that a monotone update sometimes causes a very time
consuming database update. Waiting half a day on a really fast machine for the
database to become usable again is a real showstopper.
Greetings
Florian
--
The dream of yesterday Florian Boor
is the hope of today Tel: +49 271-771091-15
and the reality of tomorrow. Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de
1D78 2D4D 6C53 1CA4 5588 D07B A8E7 940C 25B7 9A76
next prev parent reply other threads:[~2008-02-04 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 23:51 Monotone issues Richard Purdie
2008-02-03 21:03 ` Graeme Gregory
2008-02-04 2:36 ` Michael 'Mickey' Lauer
2008-02-04 8:31 ` Koen Kooi
2008-02-05 8:45 ` Paul Sokolovsky
2008-02-04 8:58 ` Florian Boor [this message]
2008-02-04 9:12 ` Rod Whitby
2008-02-04 9:48 ` Koen Kooi
2008-02-04 10:24 ` Rod Whitby
2008-02-04 10:36 ` Graeme Gregory
2008-02-04 9:52 ` Graeme Gregory
2008-02-04 11:00 ` Michael Krelin
2008-02-05 8:37 ` Paul Sokolovsky
-- strict thread matches above, loose matches on Subject: below --
2008-02-01 10:19 Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47A6D3C2.10304@kernelconcepts.de \
--to=florian.boor@kernelconcepts.de \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.