Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hi Tony,
Perhaps I'm just used to the RCS approach which ignores differences in keyword
expansion, but here's the problem I'm having...
I have some source trees that aren't under cvs that I'd like to "build" a cvs
revision history for from a set of separate directories for each release. So I
add/commit a lot of new files to the repository with the $Id$ line in it from release
1 of the code. The working copy shows it expanded in all of them. Then I drop on
the sources for release 2 of the code. If it weren't for the $Id$ expansion, the
following commit would only show as modified those sources that really ARE modified
in their source body. Instead, cvs shows all files as changed from the previous
release. I'd like ot have it act like RCS and not consider the keyword expansion in
the comparison. Any idea of how to do that?
-Gary-
Tony Hoyle wrote:
> Gary Newman wrote:
>
> > $Id: foo.cpp,v 1.1 etc... $
> >
> > if that line isn't exactly what the update provided, then the
> > update/commit commands consider the file modified.
>
> If that line isn't what the update provided, it *is* modified.
>
> I don't see what the problem is...
>
> Tony