Ambiguous commit message in cvs-1.12

[Stefan Monnier]

It seems that CVS-1.12 has changed smoe of its messages.
Such changes are very inconvenient in and of themselves for front-ends like
PCL-CVS, since you have to update the front-end to correctly parse the new
messages, but one of those changes is even worse because it makes the result
ambiguous.  Here is a sample session that shows the problem:

   $ cvs commit -m"test"
   cvs commit: Examining A
   cvs commit: Examining A/B1
   cvs commit: Examining A/B2
   /cvsroot/test/A/B1/foo,v  <--  foo
   new revision: 1.6; previous revision: 1.5
   /cvsroot/test/A/B2/bar,v  <--  bar
   new revision: 1.3; previous revision: 1.2
   $ 

Apparently two files were commited: A/B1/foo and A/B2/bar, but it's pretty
difficult to figure it out, especially given the fact that a `modules' file
might have mapped /cvsroot/test/A/B1 to A and /cvsroot/test/A/B2 to A/B1.

The old format included a line like "Checking in A/B1/foo;" which resolved
those ambiguities.

Ideally (from the point of view of PCL-CVS) the change should be reverted,
but at the very least it should be fixed to include the necessary
extra info.
One obvious possibility is to replace the "<-- foo" with "<-- A/B1/foo".


        Stefan "Maintainer of PCL-CVS"