[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dcms-dev
Subject:    Re: [opencm-dev] Repo Copy
From:       "Jeroen C. van Gelderen" <jeroen () vangelderen ! org>
Date:       2003-05-01 2:45:26
[Download RAW message or body]


On Thursday, May 1, 2003, at 04:28 Europe/Amsterdam, Steven Shaw wrote:
> The point of my suggestion - 'cm cp -noshare' - is that it preserves 
> the
> file history without subjecting the file to merges from common 
> ancestors.
> This is the essense of what CVS repo-copy hack gives you. I am not
> suggesting a hack but a legal operation which preserves file history 
> without
> changing the past.

Sure, but the essence of the CVS repo-copy doesn't seem useful. A 
repo-copy is used to try and achieve "cm cp" or "cm mv" without losing 
history. I don't see the point of being bug-for-bug compatible with the 
side-effects of a CVS hack. I think we're on the same page here though.

> If you want file2 to be subject to merges from ancestors of file1 then 
> the
> CVS repo-copy hack does not help you at all.

I want this, there is just no way to achieve it with CVS. So one 
settles for second best.

> We seem to agree that a 'cm cp' command that creates a new file with 
> shared
> ancestry would be a useful command.

Yes.

> When shared ancestry is not required
> then 'cp file1 file2; cm add file2' probably suffices even though you 
> forget
> how file2 originated - people could just use 'cm note'.

Yep. It is like adding a new file: you have to specify history by hand.

-J
-- 
Jeroen C. van Gelderen - jeroen@vangelderen.org

Hatred, n.:
   A sentiment appropriate to the occasion of another's superiority.
   -- Ambrose Bierce, "The Devil's Dictionary"

_______________________________________________
opencm-dev mailing list
opencm-dev@smtp.opencm.org
http://www.opencm.org/mailman/listinfo/opencm-dev
[prev in list] [next in list] [prev in thread] [next in thread]