From: Chmouel Boudjnah <chmouel@mandrakesoft.com>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>
Cc: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>,
zsh-workers@sunsite.auc.dk
Subject: Re: sourceforge issues
Date: 03 Apr 2000 17:14:55 -0700 [thread overview]
Message-ID: <m2em8mrabk.fsf@natanya.us.mandrakesoft.com> (raw)
In-Reply-To: "Bart Schaefer"'s message of "Mon, 3 Apr 2000 17:09:49 -0700"
"Bart Schaefer" <schaefer@candle.brasslantern.com> writes:
> In Emacs vc, `C-x C-v a' will update ChangeLog by incorporating all CVS logs
Humm no :
C-x v a runs the command vc-update-change-log
which is an interactive compiled Lisp function in `vc'.
(vc-update-change-log &rest ARGS)
Find change log file and add entries from recent RCS/CVS logs.
Normally, find log entries for all registered files in the default
directory using `rcs2log', which finds CVS logs preferentially.
The mark is left at the end of the text prepended to the change log.
With prefix arg of C-u, only find log entries for the current buffer's file.
With any numeric prefix arg, find log entries for all currently visited
files that are under version control. This puts all the entries in the
log for the default directory, which may not be appropriate.
>From a program, any arguments are assumed to be filenames and are
passed to the `rcs2log' script after massaging to be relative to the
default directory.
not control-v
--
MandrakeSoft Inc http://www.mandrakesoft.com
Pasadena, CA USA --Chmouel
next prev parent reply other threads:[~2000-04-04 0:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-03 20:45 Peter Stephenson
2000-04-03 21:50 ` Adam Spiers
2000-04-04 0:13 ` Bart Schaefer
2000-04-03 21:52 ` Clint Adams
2000-04-04 19:38 ` Peter Stephenson
2000-04-03 22:14 ` Bruce Stephens
2000-04-03 23:00 ` Zefram
2000-04-04 0:09 ` Bart Schaefer
2000-04-04 0:14 ` Chmouel Boudjnah [this message]
2000-04-04 19:31 ` Peter Stephenson
2000-04-04 1:27 ` Geoff Wing
2000-04-04 3:23 ` Clint Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2em8mrabk.fsf@natanya.us.mandrakesoft.com \
--to=chmouel@mandrakesoft.com \
--cc=pws@pwstephenson.fsnet.co.uk \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).