Hello David,
> > I just want to check in different files, that are
> > in a common _folder_, into different repositories!
> Nope; not in CVS. It would take a major redesign of CVS to make
> this possible.
Well, it became obvious quite soon, that CVS will not do it
without some tricks.
> > Also
> -Original Message-
> From: C. Wienberg [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 13, 2002 4:07 AM
> To: [EMAIL PROTECTED]
> Subject: Re: using head revision in branch after add on branch
>
>
> Hi Greg,
>
> > > You can only check them
Hi Greg,
> > You can only check them in into _one_ module.
> Of course -- that's about the only way you'll ever make any kind of
> change management system make sense!
I think there is a misunderstanding: I do not intend to check one file
into several modules! I just want to check in different
Hi Eivind,
> The following will probably work, but is DIRTY, and I am not certain
> what side effects it may have on other apps trying to interact with
> the CVS repository:
> cvs admin -N:1
It works! The command will change the symbols-entry in the *,v-File
for the branch-symbol from ":1.1.
[ On Saturday, February 2, 2002 at 09:14:40 (+0100), C. Wienberg wrote: ]
> Subject: Re: using head revision in branch after add on branch
>
> You can only check them in into _one_ module.
Of course -- that's about the only way you'll ever make any kind of
change managemen
Hi Greg,
> It all depends on where you make the changes, now doesn't it. If you
> make them in the working directory then you can just check them in.
> ...you wouldn't need to use 'cvs export'...
You can only check them in into _one_ module.
If we have one module for common stuff and one with s
[ On Friday, February 1, 2002 at 19:12:52 (+0100), C. Wienberg wrote: ]
> Subject: Re: using head revision in branch after add on branch
>
> Hi Harald,
>
> > If you've four projects which share some code, you'd better work
> > with modules.
>
> Doesn&
Hi Harald,
> If you've four projects which share some code, you'd better work
> with modules.
Doesn't work, if you have folders that contain files from different
modules. CVS assumes that all files in a sandbox folder are from
the same module. Of course, by using "export" or some clever ant-
s
On Fri, Feb 01, 2002 at 02:16:20PM +0100, C. Wienberg wrote:
> If we kill the ,v-File from the repository, andd add the file on the
> head branch, we will loose the file's history. Is there any better way?
> All we want is to get the symbolic name point to the same
> version as head!
The followi
C. Wienberg wrote:
> Hello,
> I have posted this problem before, but the proposed solutions didn't
> work.
>
> Setting: We are using CVS to store 4 projects, that use some common
> files.
> Common files are in the head branch, every Project has its own branch.
>
Well, it may not help you at t
10 matches
Mail list logo
