CVS diffs via mail

CVS diffs via mail

[Pavel Janik ml.]

Hi,

what about creating ding-cvs mailing list which will be receiving all commit
messages with diff attached? It is not always possible to got the newest
sources via CVS...
-- 
Pavel Janík ml.
Pavel.Janik@inet.cz

Re: CVS diffs via mail

[Lars Magne Ingebrigtsen]

Pavel.Janik@inet.cz (Pavel Janik ml.) writes:

> what about creating ding-cvs mailing list which will be receiving all commit
> messages with diff attached? It is not always possible to got the newest
> sources via CVS...

How does one make CVS spit out diffs each time someone commits
something? 

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: CVS diffs via mail

[Shenghuo ZHU]

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

LMI> Pavel.Janik@inet.cz (Pavel Janik ml.) writes:
>> what about creating ding-cvs mailing list which will be receiving all commit
>> messages with diff attached? It is not always possible to got the newest
>> sources via CVS...

LMI> How does one make CVS spit out diffs each time someone commits
LMI> something?

This manual page might help.

    http://www.gnu.org/manual/cvs/html_node/cvs_137.html

-- 
Shenghuo

Re: CVS diffs via mail

[Lars Magne Ingebrigtsen]

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> LMI> How does one make CVS spit out diffs each time someone commits
> LMI> something?
> 
> This manual page might help.
> 
>     http://www.gnu.org/manual/cvs/html_node/cvs_137.html

Hm.  But how does one say "give me the diffs between what was before I
checked in these last X files and what is now"?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: CVS diffs via mail

[Kai Großjohann]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Hm.  But how does one say "give me the diffs between what was before I
> checked in these last X files and what is now"?

In CVSROOT/loginfo, you can specify a script to call.  You can pass %s
to the script which is the file name.  %V is the old version number
and %v is the new version number.

You can also use `%{sVv}' to pass them all.

kai
-- 
Beware of flying birch trees.

Re: CVS diffs via mail

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> In CVSROOT/loginfo, you can specify a script to call.  You can pass %s
> to the script which is the file name.  %V is the old version number
> and %v is the new version number.
> 
> You can also use `%{sVv}' to pass them all.

But, er, isn't the logfile thing run after *all* the files in the
batch have been committed?  And, in that case, would there be a whole
lot of different version numbers?

To put it another way -- can the person(n) who want the diff mailing
list send me a script to create it?  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: CVS diffs via mail

[Kai Großjohann]

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.

Re: CVS diffs via mail

[Florian Weimer]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> To put it another way -- can the person(n) who want the diff mailing
> list send me a script to create it?  :-)

I've written such a script (in Python) for our internal use.

It's still a bit buggy, and I would like to fix it before
distribution, but I can't do that before Tuesday.  (If anyone else
comes up with a script before that date, that would be fine, too.)

BTW: It won't handle commits of new files correctly, which seems to be
difficult to fix, because "cvs rdiff" doesn't give you the proper
output for them.

Re: CVS diffs via mail

[Lars Magne Ingebrigtsen]

Florian Weimer <fw@deneb.cygnus.argh.org> writes:

> I've written such a script (in Python) for our internal use.
> 
> It's still a bit buggy, and I would like to fix it before
> distribution, but I can't do that before Tuesday.  

Okidoke.  You'll mail it to me after it's done?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen