From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: CVS diffs via mail
Date: Sat, 22 Apr 2000 20:37:40 +0200 [thread overview]
Message-ID: <200004221837.UAA05216@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "22 Apr 2000 20:24:46 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> But, er, isn't the logfile thing run after *all* the files in the
> batch have been committed?
(For the convenience of `somebody' who wants to do this.)
I have just confirmed that this is not the case. You get one message
per file, where %{sVv} expands into stuff like
'path/to/dir filename,old,new'
Note the ticks and the space and the commas. `old' and `new' are the
version numbers, of course.
Problem is: the path/to/dir changes. Suppose you have a CVS
repository /foo/cvsroot with subdirs gnus and w3.
Users who say `cvs -d /foo/cvsroot co .' will produce `gnus/lisp
gnus.el' for the path and file name. But users who say `cvs -d
/foo/cvsroot co gnus' will produce `lisp gnus.el'. Strange.
But the program that's run can read stuff from stdin, and that pretty
clearly shows which file was affected.
In my loginfo, I have the following line:
/----
| ALL /usr/bin/mailx -s "cvs ci %{sVv}" emacs-rcp@ls6
\----
I get mails like the following:
/----
| From: Kai Grossjohann <grossjoh@lucy.cs.uni-dortmund.de>
| Subject: cvs ci 'rcp/lisp rcp.el,1.274,1.275'
| To: emacs-rcp@ls6.cs.uni-dortmund.de
| Date: Sat, 22 Apr 2000 20:24:49 +0200
| X-From-Line: emacs-rcp-request@ls6.cs.uni-dortmund.de Sat Apr 22 20:27:50 2000
| Resent-From: emacs-rcp@ls6.cs.uni-dortmund.de
|
| Update of /services/emacs-rcp/cvsroot/rcp/lisp
| In directory lucy:/export/home/grossjoh/work/emacs-rcp/rcp/lisp
|
| Modified Files:
| rcp.el
| Log Message:
| Meaningless change to test the loginfo script
|
|
\----
Hope this helps as a guide.
kai
--
Beware of flying birch trees.
next prev parent reply other threads:[~2000-04-22 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-21 19:50 Pavel Janik ml.
2000-04-22 0:13 ` Lars Magne Ingebrigtsen
2000-04-22 0:21 ` Shenghuo ZHU
2000-04-22 12:16 ` Lars Magne Ingebrigtsen
2000-04-22 15:27 ` Kai Großjohann
2000-04-22 18:24 ` Lars Magne Ingebrigtsen
2000-04-22 18:37 ` Kai Großjohann [this message]
2000-04-22 22:56 ` Florian Weimer
2000-04-23 19:07 ` Lars Magne Ingebrigtsen
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=200004221837.UAA05216@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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 NNTP newsgroup(s).