info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: **help needed for CVS**


From: DHARNA, AJAY [AG/1000]
Subject: RE: **help needed for CVS**
Date: Wed, 28 Jan 2009 10:00:41 -0600

You would change the CVSROOT – in WinCVS under the Macros, you can run CVS à Change CVSROOT on the folder(s) you want to commit. Give it the old CVSROOT (your colleague userid) and replace it with yours.

 

Ajay

 

From: address@hidden [mailto:address@hidden On Behalf Of Gupta, Richa (GE Healthcare, consultant)
Sent: Wednesday, January 28, 2009 7:53 AM
To: address@hidden
Cc: Gupta, Richa (GE Healthcare, consultant)
Subject: **help needed for CVS**

 

Hi,

 

I am using CVS for maintaining versions of my code.

I had recently joined this project and my colleague gave me a code for some changes.

That piece of code was checked-out by him on his machine.

I made the changes in code and when i went to check-in the code in CVS from my machine, I found that its asking my colleague's password for checking-in.

Now my colleague has left the project and in no way i can use his password.

Also the code changes are very large in number, so I do not want to take a risk of doing them again in new code checked out by me.

 

As the code was checked-out by my colleague on his machine and I am trying to check-in through my machine and hence the problem.

Please tell me if there is any way that my problem can be solved.

I will be really grateful.

 

Thanks & Regards,
Richa Gupta

 

This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited.

All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]