Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 77058 - Would like ability to set ascii/binary commit type before first CVS commit
Summary: Would like ability to set ascii/binary commit type before first CVS commit
Status: RESOLVED DUPLICATE of bug 16793
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-26 16:58 EDT by lindor CLA
Modified: 2004-10-26 20:37 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lindor CLA 2004-10-26 16:58:44 EDT
This is a feature request:
For filetypes that CVS does not already know, it would be nice if one could 
set the ascii/binary commit type (-kkv, -ko, etc) *before* the first commit of 
a file.  Or, if this is not possible, it would be nice to be able to specify 
that certain filenames get committed in a particular way.  Right now there is 
the possibility to do this using file extensions (.cpp, .a, .exe), and this 
works very well for about 99% of the cases, but there are a few cases where 
this does not work -- in my case, most notably for "makefile"'s.  Since the 
system does not recognize these as having a known file extension (because 
makefile has no extension), CVS always defaults to binary type on the first 
commit, even though it is my desire to have these committed as ascii files.  
So, every time I have a makefile, I must fist allow Eclipse's CVS to commit it 
as binary, and then I must go back and change the file type to ascii -kkv and 
then re-commit it again.  This is not a major problem, but it is a continual 
annoyance.  If I could either (a) tell CVS that "makefile" is ascii -kkv 
*before* I do the first commit, or (b) could add "makefile" to the list of 
known ascii file types, it would be much more convenient.
Comment 1 Michael Valenta CLA 2004-10-26 20:37:00 EDT
You can do it before committing by doing an "Add to Version Control" then 
a "Change ASCII/Binary Property" and then a commit. However, this is not much 
better. Ideally, the handling of unknown types would be integrated into the 
commit.

*** This bug has been marked as a duplicate of 16793 ***