[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS bug?
Re: CVS bug?
Mon, 11 Nov 2002 11:39:28 -0500 (EST)
Damjan Zemljic writes:
> I created a branch on one file just to have that tag in CVS repository.
That's your mistake -- you need to branch an entire module, not just a
> Nothing has been commited yet to this branch. Then I've checkouted
> files with:
> cvs co -R -f -r <branch_name> <module>
> (from branch and missing from HEAD)
Using -f with checkout is almost always a mistake.
> After that, I patched the files of module and wanted to commit changes
> (excpeted to commit to <branch_name>). I got "up-to-date check failed"
> and CVS server refused to commit.
Which is exactly what should happen.
> I found out that after making branch explicitly on that file:
> cvs tag -b <branch_name> <patched_file>
> ...commit succeeded.(?!)
Correct. That's why you want to branch the entire module. You should
read the section of the manual on branching and merging:
> Is this a bug of cvs version 1.11p1 or agreed CVS behaviour. I'm pretty
> sure CVS made automaticaly branch for commited changes in previous releases.
You're pretty wrong. CVS can't read your mind -- if you want a branch,
you have to create it.
What this games needs are negotiated settlements. -- Calvin
- CVS bug?, Damjan Zemljic, 2002/11/11
- Re: CVS bug?,
Larry Jones <=