My company has just decided to start using CVS. The system admin responsible
for the CVS server is new to CVS and learning as we go along so we are
running into some problems with how to layout our repository etc ...
Please bare with me as I try and explain our situation :)
We're trying to have t
> From: [EMAIL PROTECTED]
>
> Using your terminology,
> > cvs co A
> > cvs update -j A -j A_DEV
> (Resolve conflicts, if any)
> > cvs commit
That doesn't seem to work. I get:
$ cvs co A
[snip]
$ cvs -n update -j A -j A_DEV
cvs server: WARNING: global `-l' option ignored.
Carter Thompson writes:
>
> What's the best way to go about resolving this error? I've tried to
> find problems
> directly with the RCS file itself but I've been unable to find anything
> wrong with
> it and I'm afraid that I'm missing something obvious.
That error does, indeed, mean that the RC
Hi,
I have a file that I'm getting an abort from cvs log on in my
repository.
$ cvs log
appspack/oracle/ig/modules/ar/install/sql/obtig_ar_filter_pb.sql
cvs [log aborted]: unrecognized operation '\x73' in
/export/cvs/prodops/appspack/oracle/ig/modules/ar/install/sql/obtig_ar_f
ilter_pb.s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Pumford <[EMAIL PROTECTED]> writes:
> Just spotted a slight interoperability problem
> with Tortoise CVS and CVS 1.12.9. The new date
> formatting code confuses the Tortoise cvs log
> output parsing code as the new local time
> formatting of date
[EMAIL PROTECTED] wrote:
> Floating tags can also be used. For example, create a tag
> called PRODUCTION and apply it to the next release. Then
> just run "cvs update"
> in the production area, and the proper versions will appear.
Yep, that's basically the idea I was trying to get across.
> Th
>--- Forwarded mail from [EMAIL PROTECTED]
>Jean-Christian Imbeault wrote:
>> One of our developers just checked in new code (more than
>> once) and by mistake renamed a directory from src to source.
>>
>> Is there a simple way to undo this? I've been reading the
>> archives and it seems that t
>--- Forwarded mail from [EMAIL PROTECTED]
>Don Butts wrote:
>> I asked this question last Friday but got no response.
>> Was it poorly asked, not enough information, too ignorant for
>> words?
>I wouldn't remove the branches. I'm always reluctant to remove anything from
>the history.
>Instead
Normally one would apply a tag to the versions that are ready for testing,
and update the tag as bugs are fixed. Then apply a second tag to the
code that reaches production quality. To apply the second tag, use the
"cvs rtag -r" option.
The bummer with this is that if you make bug fixes in your
> Don Butts wrote:
>
> Content-Type: multipart/mixed; boundary="===1243246784=="
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
> We are using cvs in somewhat of a non-standard way.
> We have a production cut of our compiled source t
Using your terminology,
> cvs co A
> cvs update -j A -j A_DEV
(Resolve conflicts, if any)
> cvs commit
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]
>] On Behalf Of Jean-Christian Imbeault
>Sent: Wednesday, June 23, 2004 2:36 AM
>T
Jean-Christian Imbeault wrote:
> One of our developers just checked in new code (more than
> once) and by mistake renamed a directory from src to source.
>
> Is there a simple way to undo this? I've been reading the
> archives and it seems that there isn't ...
Um, is it too obvious to suggest re
Don Butts wrote:
> I asked this question last Friday but got no response.
> Was it poorly asked, not enough information, too ignorant for
> words?
How about, this requires a few more brain cycles than were available at the
time? :=)
> -Original Message-
> We are using cvs in s
At 09:07 AM 6/23/2004, Ramanuj Singh wrote:
The information transmitted is intended only for the person or entity to
whom it is addressed and may contain confidential and / or privileged
Material. Any review, re-transmission, dissemination or other use of or
taking of any action in reliance upon
Title: branch removal question
I
asked this question last Friday but got no response.
Was it
poorly asked, not enough information, too
ignorant for words? If I need to supply more
information
please
let me know, I would be glad to.
Thanks,
Don
Butts
-Original Message
[EMAIL PROTECTED] wrote:
> Jeeva Sarma writes:
> >
> > I have a question using cvs admin command to delete a revision of a
> > file. If I deleted revision 1.7 of a file, which also exists on a
> > branch at that revision, what will be the status of that
> file on the
> > branch?
>
> A revisio
Hi,
I have to delete a user from cvs. Is it possible I can lose
any information about that user rcs files or the history file.
By information I mean the operatons that user performed on
the projects in cvs repository before its deletion.
The second thing , I wanna know that I don'
Just spotted a slight interoperability problem with Tortoise CVS and CVS
1.12.9. The new date formatting code confuses the Tortoise cvs log output
parsing code as the new local time formatting of dates end up using - to
separate the year/month/day fields instead of the / used in older versions
At 03:16 AM 6/23/2004, Jean-Christian Imbeault wrote:
renamed a directory from src to source
What cvs command did the developer use to do this? I didn't think this was
possible.
Fred
___
Frederic W. Brehm, Sarnoff Corporation, http://www
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christian Imbeault <[EMAIL PROTECTED]> writes:
> At my company we have a repository with two
> projects (I hope I have the terminology right).
> One project is A and the other is A_DEV.
I suspect you mean 'module' here, but sure,
calling it a 'p
One of our developers just checked in new code (more than once) and by
mistake renamed a directory from src to source.
Is there a simple way to undo this? I've been reading the archives and it
seems that there isn't ...
Thanks,
Jean-Christian Imbeault
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sandhya <[EMAIL PROTECTED]> writes:
> I received good mails about locking files and I
> was able to understand that its quite impossible
> in CVS.
Well, advisory locks are possible, but generally
considered undesirable.
> Now What I want to know is
22 matches
Mail list logo
