monotone-devel
[Top][All Lists]
Advanced

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

[Monotone-devel] Re: [Monotone-commits-diffs] Revision c6569e455defcd6b0


From: Chad Walstrom
Subject: [Monotone-devel] Re: [Monotone-commits-diffs] Revision c6569e455defcd6b0d889edcff0bb0fe6180a376
Date: Thu, 01 Sep 2005 08:55:53 -0500
User-agent: Debian Thunderbird 1.0.2 (X11/20050817)

Richard Levitte wrote:
See http://ximbiot.com/cvs/wiki/index.php?title=CVS--Concurrent_Versions_System_ v1.12.12.1:_Tracking_third-party_sources

I think you could get much the same thing by simply proving the BRANCH for the vendor when you commit the upstream sources.

OK, that's an opinion. I still maintain that a command the just adds a MT directory with contents to the designated directory will confuse most of the world (and particularly those who went in CVS school, which should be quite a lot of people).

I actually found it quite refreshing to simply go to an existing project directory, type "monotone -d $DATABASE setup", "monotone ls unknown|xargs -r monotone add", and "monotone -b BRANCH commit".

I think by "most of the world", you mean "CVS-users of the world". Most people of the world would walk through the tutorial to find out how to use the tool and realize that there are multiple steps. Most people of the world would probably compare the tutorials of a couple SCM's and realize that most of them use a multiple-step process to "import" new source.

It maybe a few steps, but it's not rocket science. If you really want to mirror the "import" step, add the "vendor tag" and "release tag".

Chad





reply via email to

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