From: rmolen@socal.rr.com (Richard V. Molen)
Subject: Re: ChangeLog and Version Control
Date: Thu, 26 Sep 2002 21:34:53 GMT [thread overview]
Message-ID: <m34rccfn9f.fsf@tsunami.socal.rr.com> (raw)
In-Reply-To: 5lelbgmzx3.fsf@rum.cs.yale.edu
Thanks Aman, this was what I was looking for. I hacked up an
alternative that doesn't prompt -- "if it's the ChangeLog, don't add
the comment." (see below). It's the "I'm not an ELisper" version, but
it seems to work. Improvements are welcome.
It would be even nicer if I could keep the ChangeLog from 'popping up'
each time -- summary comments could be added explicitly w/ C-x 4 a.
Thank you Kai for your comments on C-x 4 a -- I'll have to try that
approach. It has more features than I realised.
******************************
;asks whether to automatically insert last Version control log entry into
;ChangeLog & allow ChangeLog editing. Answer 'n' after C-x C-q...C-c C-c
;of ChangeLog to prevent adding its log entry to itself.
(defun vc-checkin-add-log-no-prompt ()
(let ((log (find-change-log)))
(and log
(not (string-match
(format "%s" (file-relative-name log))
(format "%s" (file-relative-name buffer-file-name))))
(vc-comment-to-change-log nil log))))
(add-hook 'vc-checkin-hook 'vc-checkin-add-log-no-prompt)
(setq vc-command-messages t ;display version control backend messages?
vc-initial-comment t ;request initial log entry when adding a file.
)
******************************
--
Richard V. Molen
Warning!!
Signature under construction, safety glasses required.
next prev parent reply other threads:[~2002-09-26 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 6:59 ChangeLog and Version Control Richard V. Molen
2002-09-26 8:24 ` 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 [this message]
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=m34rccfn9f.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).