RE: Future CVS Development

[Noel L Yap]

Yup, I would probably implement it with something like /etc/magic instead of
matching file extensions, though.

Noel


|--------+----------------------->
|        |                       |
|        |          address@hidden|
|        |          to.com       |
|        |                       |
|        |          06/19/01     |
|        |          12:56 PM     |
|        |                       |
|--------+----------------------->
  >----------------------------------------------------------------------------|
  |                                                                            |
  |       To:     address@hidden, address@hidden                   |
  |       cc:     address@hidden, (bcc: Noel L Yap)                          |
  |       Subject:     RE: Future CVS Development                              |
  >----------------------------------------------------------------------------|






> -----Original Message-----
> From: Noel L Yap [mailto:address@hidden
> Sent: Tuesday, June 19, 2001 8:49 AM
> To: address@hidden
> Cc: address@hidden
> Subject: RE: Future CVS Development
>
>
> CVS only requires files to be mergable.  This has a different
> meaning from
> requiring files to be non-binary.
>
> One thing that may be done is to add a hook for pluggable
> diffing/merging
> engines.

Now, pluggable engines would be truly cool!  I know that one large argument
against CVS here (my office) was that it doesn't do "intelligent" things
with proprietary format non-mergable files (like MSWord documents), where
other source control systems can do (the counterexample was always
Clearcase).  But if you could plug in a diff/patch tool for *.doc files,
(and perhaps a different diff/patch tool for *.ppt, another for *.xls) that
would make these files mergable, and thus behave sensibly in CVS! :)




This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.