Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community ForumsPrevent file from being commited to CVS
https://www.eclipse.org/forums/index.php/mv/msg/161167/509364/#msg_509364
1. I have made some local changes to a file that is under CVS control
2. I know that I will never (and should not!) commit these changes back to CVS (e.g. I activated some debug code that is only necessary for local debugging)
What I want is to "lock" the file locally. That is, I am not able to commit this file to CVS. But a CVS sync will still show me if a new version exists (and I can merge locally). Of course, I should be able to remove the lock when I reverted my temporary changes.]]>Axel Mueller2010-01-22T09:20:05-00:00Re: Prevent file from being commited to CVS
https://www.eclipse.org/forums/index.php/mv/msg/161167/509578/#msg_509578
> Regard the following scenario:
> 1. I have made some local changes to a file that is under CVS control
> 2. I know that I will never (and should not!) commit these changes back
> to CVS (e.g. I activated some debug code that is only necessary for
> local debugging)
>
> What I want is to "lock" the file locally. That is, I am not able to
> commit this file to CVS. But a CVS sync will still show me if a new
> version exists (and I can merge locally). Of course, I should be able to
> remove the lock when I reverted my temporary changes.
In 'Team Synchronizing' perspective, right click on an outgoing change
-> add to .cvsignore.]]>Deepak Azad2010-01-23T07:27:25-00:00Re: Prevent file from being commited to CVS
https://www.eclipse.org/forums/index.php/mv/msg/161167/510323/#msg_510323
Quote:
In 'Team Synchronizing' perspective, right click on an outgoing change
-> add to .cvsignore.
But wouldn't the .csvignore file be committed to the CVS server? Thus, everybody else would not be able to commit this file? As mentioned before, the file in question is already under CVS control, I just want to make the sure that my temporary changes are not committed accidentally.]]>Axel Mueller2010-01-27T09:34:31-00:00Re: Prevent file from being commited to CVS
https://www.eclipse.org/forums/index.php/mv/msg/161167/510693/#msg_510693
bug 112549 which looks similar.]]>Tomasz Zarna2010-01-28T11:06:13-00:00Re: Prevent file from being commited to CVS
https://www.eclipse.org/forums/index.php/mv/msg/161167/511234/#msg_511234
> Quote:
>> In 'Team Synchronizing' perspective, right click on an outgoing change
>> -> add to .cvsignore.
>
> But wouldn't the .csvignore file be committed to the CVS server? Thus,
> everybody else would not be able to commit this file? As mentioned
> before, the file in question is already under CVS control, I just want
> to make the sure that my temporary changes are not committed accidentally.
Add .cvsignore to .cvsignore as well.]]>Deepak Azad2010-01-31T15:50:06-00:00Re: Prevent file from being commited to CVS
https://www.eclipse.org/forums/index.php/mv/msg/161167/511302/#msg_511302
Quote:
In 'Team Synchronizing' perspective, right click on an outgoing change
-> add to .cvsignore
Unfortunately, the .cvsignore trick does not work. Eclipse greys out the "Add to .cvsignore" option if the file is already under CVS control. Manually adding the file to .cvsignore does not work either. It seems .cvsignore (and Eclipse) ignores files that are under CVS control. The same holds for the Team>Ignored Resources preference page.
Quote:
please have a look at bug 112549 which looks similar.
There are some similarities between my request and this bug, but I guess I have to open a new bugzilla request.
(see https://bugs.eclipse.org/bugs/show_bug.cgi?id=301389)]]>Axel Mueller2010-02-01T08:20:22-00:00Re: Prevent file from being commited to CVS
https://www.eclipse.org/forums/index.php/mv/msg/161167/513304/#msg_513304
> Quote:
>> In 'Team Synchronizing' perspective, right click on an outgoing change
>> -> add to .cvsignore
>
> Unfortunately, the .cvsignore trick does not work. Eclipse greys out the
> "Add to .cvsignore" option if the file is already under CVS control.
> Manually adding the file to .cvsignore does not work either. It seems
> .cvsignore (and Eclipse) ignores files that are under CVS control.
By the way, that's a feature of cvs (not Eclipse-specific); once a file
is known in the repository it can't be ignored. I suppose an
administrator could manually remove it from the repository, which makes
cvs "forget" that it ever knew the file. But IIUC that's not a solution
to the original problem discussed here.