[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Commit

From: Brian Behlendorf <brian_at_collab.net>
Date: 2001-09-04 23:17:53 CEST

On 4 Sep 2001, Ben Collins-Sussman wrote:
> Brian Behlendorf <brian@collab.net> writes:
> > E.g.
> >
> > Subject: commit: trunk/subversion/clients/cmdline diff.c diff-cmd.c
> > trace-update.c propget-cmd.c propset-cmd.c
> Maybe you disagree with us here; we don't think seeing a list of 10+
> files in a subject line is useful. It's just a lot of clutter.

I follow the commit lists on about 20 projects, into my main inbox. When
I start reading email in the morning I sort by subject to follow threads,
sometimes surfing the thread index looking for interesting things to
start. A subject line that tells me what project the commit was for
(trunk/subversion) and what rough section of the code (clients/cmdline) is
very useful to me, both for subject-line-surfing reasons and for grouping
together commits around related parts of code. This is also true for
those commit lists I channel off to side mailboxes and read once a month
or so. So this goes beyond just threading.

> > b) could we set the "from" header to come from user@devhost? Either
> > something like joe@svn.collab.net, or since this is the same UID as on
> > tigris.org, joe@tigris.org...
> Hmmm. Right now, httpd is running as user "svn", and thus this is the
> user that is exectuing the post-commit mail script. Maybe there are
> options the script could pass to /usr/bin/mail that change the "from"
> header? Anyone?

Just put a "From:" header in the commit message, above the Subject line,
and that should be good enough, no? At least that works if you call
sendmail instead of mail, which I would do anyways...


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:40 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.