|Subject:||RE: CVS Import|
|Date:||Fri, 3 Aug 2001 14:24:23 -0400|
Thank you very much Larry, the import went exactly as desired including the core module.
I want to seek one more clarification \ misunderstanding
1) I do import #1 of a module into the CVS repository. --- as per the regular import command and all its parameter such as dir to import into, vendor name and release tag.
2) Then I do a import #2 of the same module but with code changes and use the same vendor name but diff release tag.
3) Now I do cvs co -jreleasetag1 -jreleasetag2 module name.
4) do a cvs commit module name.
What is cvs doing actually with this commit?
Is it same as committing the changes I do on the branch back on to the trunck?
But here which code is part of the trunck.
From: address@hidden [mailto:address@hidden]
Sent: Monday, July 23, 2001 3:31 PM
Subject: Re: CVS Import
Rajesh Patwardhan writes:
> Q1) The module named "core" simply refuses to be imported in to CVS. I would
> be really grateful for any help or directions or workarounds to this
> problem. Server \ Client 1.11.1p1 on Linux as well as Solaris.
> Observed : The import starts off with I ( capital I)
> path_to_core_module/core and then further does not import anything in that
The "I" means that it is being ignored. "core" is on the default ignore
list because that's the name traditionally used on Unix for core dumps.
If you really want to import something named core, you'll have to use
the -I option to import to override the default ignore list:
> Q2) During import I find that the binary files are not correctly imported.
Please provide more details. You can use the -W option to import to
specify filename patterns that are to be treated as binary:
TIME?! I just finished the first problem! -- Calvin
Info-cvs mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|