From: | Neil Conway <neilc(at)samurai(dot)com> |
---|---|
To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: commit messages from gforge -> pgsql-committers |
Date: | 2004-05-20 19:38:27 |
Message-ID: | 40AD0933.2010406@samurai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Marc G. Fournier wrote:
> I can't see this really being possible ... have you seen this on another
> project?
Sure, it's quite common. There's a list of scripts that support this
kind of functionality at the bottom of this page:
http://www.badgers-in-foil.co.uk/projects/cvsspam/
So there are plenty of alternatives to choose from. For example, David
Wheeler's "activitymail" can be instructed via a command-line argument
to include inline diffs, or include diffs as attachments:
http://search.cpan.org/~dwheeler/activitymail/
(that functionality described in "README")
Whereas "cvslog" seems to support both including the entire diff with
the message or including CVSWeb URLs:
http://www.eyrie.org/~eagle/software/cvslog/
> For the really simple commits, sure ... but for the more complex
> ones, we'd been talking a load of URLs, for each of the different files
> being updated ...
Personally I'd prefer the entire diff to be attached to each -committers
mail, which would circumvent this problem. Would others find that
objectionable?
-Neil
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Jensen | 2004-05-20 20:07:34 | Re: commit messages from gforge -> pgsql-committers |
Previous Message | Bruce Momjian | 2004-05-20 19:29:28 | Re: [HACKERS] Configuration patch |