Title: Sharing Files
I am a new user to CVS, I was formerly using Visual SourceSafe. It has a feature where a single file may be shared between several locations. For example file X is used in project A and project B. Therefore I would like file X to appear in the directories for Project A
Hello,
I want to use a modular approach for settting up a CVS-repository. Unfortunately, I can not get it to work as I want. I have read both the Cederqvist and the Fogel document, but the 'modules' file (which I think must be used for file sharing) is not very extensively explored in both d
On Fri, May 24, 2002 at 08:59:24AM -0600, Kendra Curtis wrote:
> I would like
> file X to appear in the directories for Project A and B so when it is
> changed in one location the changes will also appear in the other.
>
> Can you do this with CVS?
You can do it for whole directories, but not fo
In there any way to tweak a file so that it's shared between all branches?
TIA
- russ -
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Hi,
Is there a way to share a single source file across multiple directories in CVS, so
that if it gets committed/merged in one directory the update registers in both
locations? I know that VSS has this concept, and was wondering if CVS offers any sort
of similar functionality. I was thinking
Hi there. :) I'm fairly new to cvs from an admin perspective, and I've
got what I hope is a pretty easy question. We've got a number of
headers files, etc that need to be available for building a number of
different applications. We need to be able to get all of the header
files easily without
A bit of a delayed response, I know...
At 02:33 PM 9/25/2002, Matt Lyon wrote:
> Is there a way to share a single source file across multiple
> directories in CVS, so that if it gets committed/merged in one
> directory the update registers in both locations? I know that VSS has
> this concept,
Russ writes:
>
> In there any way to tweak a file so that it's shared between all branches?
No.
-Larry Jones
Nobody knows how to pamper like a Mom. -- Calvin
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
> Is there a way to share a single source file across multiple
> directories in CVS, so that if it gets committed/merged in
> one directory the update registers in both locations? I know
> that VSS has this concept, and was wondering if CVS offers
> any sort of similar functionality. I was th
At 02:33 PM 9/25/2002, Matt Lyon wrote:
>Is there a way to share a single source file across multiple directories
>in CVS, so that if it gets committed/merged in one directory the update
>registers in both locations? I know that VSS has this concept, and was
>wondering if CVS offers any sort o
> >> Is there a way to share a single source file across multiple
> >> directories in CVS, so that if it gets committed/merged in
> >> one directory the update registers in both locations? I know
> >> that VSS has this concept, and was wondering if CVS offers
> >> any sort of similar function
>--- Forwarded mail from [EMAIL PROTECTED]
>> Is there a way to share a single source file across multiple
>> directories in CVS, so that if it gets committed/merged in
>> one directory the update registers in both locations? I know
>> that VSS has this concept, and was wondering if CVS offer
I have found that it is ok to symlink *directories* in the CVS repository,
but you should not symlink individual files. CVS uses locks on a
per-directory basis to handle concurrency, and linking a file across
directories allows multiple cvs processes to access the file simultaneously
and possibl
Why can't you place the header files in their own module, and include
that module in another one, using either the -a or & operators?
Another method that's used successfully is to create baselines to which
developers create references. Your symlink method is one way to do it,
but there are other
Hi all,
I setup a CVS server (version 1.10.6) a while back, and I now have the need
to share some files between projects.
The files are test data that does not change between projects, so I do not
want to duplicate it in the repository.
Previously, I used VSS' sharing mechanism to accomplish this
>--- Forwarded mail from [EMAIL PROTECTED]
>I setup a CVS server (version 1.10.6) a while back, and I now have the need
>to share some files between projects.
>The files are test data that does not change between projects, so I do not
>want to duplicate it in the repository.
>Previously, I used V
[ On Saturday, February 26, 2000 at 13:18:45 (-0800), Paul Sander wrote: ]
> Subject: Re: removing the need for "cvs add file" to contact the server
>
> One of the requirements of this architecture is to share header files
> across multiple projects. (Such a project would also contain librari
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Saturday, February 26, 2000 at 13:18:45 (-0800), Paul Sander wrote: ]
>> Subject: Re: removing the need for "cvs add file" to contact the server
>>
>> One of the requirements of this architecture is to share header files
>> across multiple proj
[ On Sunday, February 27, 2000 at 01:25:39 (-0800), Paul Sander wrote: ]
> Subject: Re: use of CVS modules for sharing files considered highly dangerous!
>
> Nope, absolutely not. Shops that use the modules database in the way I
> have described have at least acknowledged that softw
19 matches
Mail list logo
