I did not see such a thing like 'certs' with other version control
systems (I could obviously be wrong on this), but, because certs allow
for many different types of user defined workflows, it is exactly the
reason why I started using monotone.
There is a learning curve involved when dealing with
On Wed, Nov 29, 2006 at 09:16:10PM -, Boris 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 w
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 "
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 dif
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'
