Description Jean-Michel Lemieux 2001-10-11 14:24:32 EDT

We currently turn off keyword substitution (-kb) for all resources we
	add to cvs. This should be configurable.

NOTES:

Jean-Michel (5/20/01 10:54:57 PM)
	This affects open source developer a lot. We should consider the effects of sending kb in the
	entry line all the time. If we want to send the right thing, we will have to persist in our sync info.
	If we leave this off, existing open source projects will be broken if they depend on keyword
	substitution.

KM (5/22/01 9:44:17 PM)
	We are not going to support keyword substitution.
	However we need to test what happens if files are already setup with keyword
	substitution and they check them in/out with our client.

TPE (2001-05-23 09:08:53)
	The crux of the problem is not knowing which resources to treat as binary and which
	to treat as text.  Treating all files as binary necessitates avoiding keyword expansion.

	Furthermore, treating all files as binary means there will be no end-of-line conversion
	for text files between Unix and Windows.  This problem will be left up to the editors/builders
	to figure out.

	Right now we have to treat all files as binary and send -kb.  As J-M noted this may be
	problematic for some projects, but remember that the platform is not a CVS GUI, it is a
	resource manager.  It tries to be a good CVS client (i.e. user) and has some shortcomings,
	of which this is one.

	The solution is to mark resources as binary/text in the platform then they can be dealt
	with correctly in various situations.

Jean-Michel (9/18/01 8:59:48 AM)
	Agreed that we need a platform level concept of binary/text files. This is not only needed
	for CVS but also for the compare framework which currently has to guess if a file is text
	or not if it does not understand the extension.

	Another problem is that in CVS files marked as binary cannot be merged with the CVS
	command line tool. This makes Eclipse CVS incompatible with command line users.