monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Tracking an "vendor branch"


From: Kevin Greiner
Subject: [Monotone-devel] Tracking an "vendor branch"
Date: Wed, 6 Apr 2005 23:04:28 -0400

I've been lurking here for a couple of months. Given Microsoft's very expensive pricing on their not-yet-released Team System development revision control package, I decided to try & learn more about monotone.

I am attempting to familiarize myself with monotone by tracking a Visual SourceSafe repository. I think some version control systems call this making a "vendor branch." My plan is synch MT and VSS at each point release. I got as far as the following.

1. Copy the 3.0 source tree to a local working directory (say "src") beneath a properly init'd MT directory and run the following commands.
mt add src
mt --branch=com.bar.foo.ver3 commit --message="version 3.0"
mt tag 884f "Foo 3.0 release"

2. Now what? I have a copy of the 3.1 source tree but what do I do with it? The manual (bottom of page 12) says that MT can't deduce file or directory adds, deletes, or renames. But I'm really not interested in manually determining which files were added or renamed between 3.0 and 3.1. I mean, there could be dozens of file changes. Surely there is a better way!

Thanks in advance for your help,

Kevin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]