Re: ANNOUNCE: Debian build scripts on a public Monotone server

[Martin Krischik <krischik@users.sourceforge.net>]

Ludovic Brenta schrieb:

>> I find it interesting in Monotone you can commit changes even if your
>> tree is not up-to-date, so you only commit your changes first go, and
>> then you do the merge. As opposed to being forced to do both in the
>> one commit (I never liked this model).
> 
> That's funny because it took me a little while to get used to the
> "commit first, merge then" model.  I wasn't used to it.  Now I like it
> quite a lot.

That's exactly was I was always looking for. I just hate how most vcs 
force me to mess up my perfectly good code by forcing me to merge when I 
am not yet ready for merge. Worse: I won't have a backup copy of the 
pre-merge code.

Yes, those vcs will mess up my working copy with ".#" files - but that 
is not the same as having a backup inside the repository.

The other option I am often missing is a "golden code" option. What I 
have prepared inside the working copy is right and propper - no merge 
needed - thank you very much.

Martin