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

[Brian May <bam@snoopy.apana.org.au>]

>>>>> "Martin" == Martin Krischik <krischik@users.sourceforge.net> writes:

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

Same here - occasionally at my previous job (they used subversion) it
was almost like a race to commit my changes first so I wouldn't have
to deal with the conflicts. Didn't always work as planned though, as
often the second person would accidently revert my changes by doing an
update operation with the file still open in the editor. "Why did you
revert my changes? The bug I fixed came back again. Did I break
something?" "I didn't revert your change!" "Yes you did, in revision
XYZ!"

Creating a fork, and then dealing with the merge operation, later,
when ready, would appear to be a much better strategy.
-- 
Brian May <bam@snoopy.apana.org.au>