[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How are you using (local) version control and comments?

From: Phillip Lord
Subject: Re: How are you using (local) version control and comments?
Date: 19 Nov 2002 12:15:15 +0000
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.92

>>>>> "Mac" == Mac  <> writes:

  Mac> Hello,

  Mac> I have found a bunch of nifty ideas from this group on how to
  Mac> use version control in Emacs. But I'm fairly new as a regular
  Mac> user of cvs and can not get it all to work out into a smooth
  Mac> flow.

  Mac> Would anyone care to help me by describing your way of working?
  Mac> I'm particularily interested in how to record changes.

  Mac> I have earlier used ediff to view differences while writing the
  Mac> commit log message.  Now I prefer to use C-x 4 a
  Mac> ('add-change-log-entry-other-window' suggested by kai) to
  Mac> record my purposes while editing the file.

  Mac> I'm currently using a Change-Log in each directory, describing
  Mac> changes in local files, and a "module specific" Change-Log in
  Mac> the top directory. But when using commit from pcl-cvs on the
  Mac> whole module, I have to manually copy and edit entries from all
  Mac> Change-logs below.

Emacs provides various tools for maintaining change logs. In
particular from vc-update-change-log generates a log for the current
directory. This is good if you want your change log to directly
reflect the version control system. 

Personally I used "" which I am sure google can find for you,
which generates a single change log for a directory structure. 

  Mac> Since I have a slow connection to my cvs repository
  Mac> (sourceforge) I'm also thinking about using RCS as a local
  Mac> version control as described in
  Mac> <info://emacs/Local+Version+Control>. Does this also work under
  Mac> pcl-cvs?

Sadly not, at least not to my knowledge. As the name suggests pcl-cvs
works with CVS. RCS does work with VC though, so emacs will still be
aware of the status of files, and you can check in and so forth. But
you won't get the full directory functionality. 

Of course CVS can work on a local machine as well, through the local
file system. This is very easy to set up, and saves messing around
with pserver. It goes something like....

mkdir ~/cvs-repository
cd ~/cvs-repository
cvs init

and then cvs -d ~/cvs-repository co

or whatever cvs command you want to use. The only reason that I use
RCS is because the version files go with the work files, which is
handy if you want to access version information later, at home for



reply via email to

[Prev in Thread] Current Thread [Next in Thread]