you can always use mtn log (or viewmtn) to look to see what is in your repository, which is completely independent of your workspace. however determining which revisions will be involved in a workspace update is a little trickier.
To my knowledge there is neither a "mtn update --dry-run" nor a "mtn log --not-in-workspace" but i'm no expert and hopefully I'm wrong about that. RS On 11/29/06, Boris <[EMAIL PROTECTED]> wrote:
I'm looking for a new revision control system and I'm very impressed from monotone so far. I read the documentation and understand how the development process looks like. I've some questions though: After synchronizing how do I see what changes came in? I can do a 'mtn update' but then 'mtn diff' doesn't show me anything. Is there a way to see what another developer actually changed (the one my database was synchronized with) before or after I update my workspace? How should software development in a team be organized ideally? Shall I use several branches? I ask as I might not want to accept every change a developer came up with. Currently I can only do a 'mtn update' and whatever was synchronized ends up in my workspace. Do I miss anything? Or is this just the way monotone works? Thanks in advance, Boris _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
