Re: Emacs and CVS

[Sergei Organov]

Seb <address@hidden> writes:
> Hi Sergei,
>
> Thanks for your suggestions.
>
>
> On Mon, 29 Jan 2007 13:08:14 +0300,
> Sergei Organov <address@hidden> wrote:
>
> [...]
>
>> pcl-cvs in general shows the results of the last operation you've
>> made. If it was cvs-update, then it shows the changed files. Use
>> cvs-status to see status of all the files, though in ~10 years of
>> programming using pcl-cvs, I never got a desire to use it. In fact it's
>> much more convenient that pcl-cvs usually doesn't show thousands of
>> files I don't care about.
>
> I'll probably veer towards that workflow, but being a newbie with CVS, I
> feel nervous not seeing all my files and their status in my checked out
> modules.

Hopefully you can still see all your files in dired ;)

I'd be prepared to change your workflow as usual workflow with CVS
should be different from those with RCS, I think (though I never used
RCS). I use usual Emacs ways to work with files, and pcl-cvs to work
with *changes*.

>>> 2. I'd like to keep using vc's changelog features ('C-x v a') for doing
>>> the changelog entries, but the author and email info are lost (this
>>> doesn't happen with RCS):
>
>> Can't help with that. I personally use add-change-log-entry, and it does
>> work for me.
>
> What I like about 'C-x v a' is that I can quickly commit a single file and
> add a file(even a function)-specific log entry.  What do you like better
> about add-change-log-entry?

Using CVS, I add changelog entries *before* commit, and then commit
all the changed files along with ChangeLog(s) in one shot. As far as I
remember, there even exists a way to copy comments from ChangeLog(s) to
the commit message automatically, but I didn't bother to learn it, as
usual copy/paste works quite nice anyway.

-- Sergei.