From: rmolen@socal.rr.com (Richard V. Molen)
Subject: ChangeLog and Version Control
Date: Thu, 26 Sep 2002 06:59:40 GMT [thread overview]
Message-ID: <m3bs6lqlrb.fsf@tsunami.socal.rr.com> (raw)
When using version control C-x C-q to check in (commit) a file into a
CVS repository, a buffer is presented in which to enter comments about
that change. C-c C-c then does the actual checkin and then presents
the ChangeLog with an entry automatically filled in. So far so good.
However, a C-x C-q on the ChangeLog pops up a the log buffer and C-c C-c
presents the re-revised ChangeLog again...
So, how do I keep the ChangeLog under CVS control and avoid this cyclic
behavior?
Perhaps there's a better method. I wonder how others maintain version
histories.
--
Richard V. Molen
Warning!!
Signature under construction, safety glasses required.
next reply other threads:[~2002-09-26 6:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 6:59 Richard V. Molen [this message]
2002-09-26 8:24 ` ChangeLog and Version Control Kai Großjohann
2002-09-26 8:39 ` Aman S Kohli
2002-09-26 14:29 ` Kai Großjohann
2002-09-26 17:19 ` Stefan Monnier <foo@acm.com>
2002-09-26 21:34 ` Richard V. Molen
2002-09-27 7:08 ` Aman S Kohli
2002-09-27 15:42 ` Richard V. Molen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3bs6lqlrb.fsf@tsunami.socal.rr.com \
--to=rmolen@socal.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).