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

Re: Email Notifications

From: S I <xiamak_at_hotmail.com>
Date: 2005-08-25 00:30:02 CEST

Ok, I downloaded the source code and I'm looking in \tools\hook-scripts and
see a file by this name: commit-email.pl.in What's .in at the end, do you
know? Or did I download the wrong version? I also do not see a file named,
post-commit. Do I need to write this file from scratch?

----Original Message Follows----
From: William Nagel <bill@stagelogic.com>
To: "S I" <xiamak@hotmail.com>
CC: users@subversion.tigris.org
Subject: Re: Email Notifications
Date: Wed, 24 Aug 2005 17:13:15 -0500
MIME-Version: 1.0 (Apple Message framework v733)
Received: from tigris.org ([64.125.133.100]) by MC6-F2.hotmail.com with
Microsoft SMTPSVC(6.0.3790.211); Wed, 24 Aug 2005 15:14:36 -0700
Received: (qmail 26277 invoked by uid 5000); 24 Aug 2005 22:13:24 -0000
Received: (qmail 26261 invoked from network); 24 Aug 2005 22:13:23 -0000
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
Mailing-List: contact users-help@subversion.tigris.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
list-help: <mailto:users-help@subversion.tigris.org>
list-unsubscribe: <mailto:users-unsubscribe@subversion.tigris.org>
list-post: <mailto:users@subversion.tigris.org>
Delivered-To: mailing list users@subversion.tigris.org
References: <BAY105-F222A89FDA6A15D74B193BD8A80@phx.gbl>
X-Mailer: Apple Mail (2.733)
X-Provags-ID: perfora.net abuse@perfora.net
login:412c950e8d3f0bd9879fcad94a7c3fa4
Return-Path: users-return-37404-xiamak=hotmail.com@subversion.tigris.org
X-OriginalArrivalTime: 24 Aug 2005 22:14:36.0680 (UTC)
FILETIME=[36A17080:01C5A8F9]

On Aug 24, 2005, at 5:05 PM, S I wrote:

>Hi all,
>
>We just switched from CVS to SVN and this is all new and foreign to me.
>Iíve read most of the SVN manual and except one vague reference to Email
>Notifications which happens to be a popular topic in demand by most of us
>daily users, thereís absolutely NOTHING mentioned about this subject in
>the manual or tigris.orgís website.
>
>Iíve also dug through the Mailing List and I find it very hard to
>comprehend, stitch, or make heads or tails of the disparate posts. I find
>the posts or their content definitely not for beginners (yours truly) and
>they only make me more confused. It beats me why the .PDF manual is not
>updated with this valuable information because I see people repeatedly
>posting to the Mailing List and inquiring about it.
>
>Could someone please tell me in steps, bullet points, or synopsis what
>exactly needs to be done to turn on notifications so a few of my
>developers could get notifications based on commits only? I know UNIX
>Linux shell scripting and Perl. I donít know any Python, sorry. I
>appreciate all your help.

Subversion doesn't have built in support for email notification. Instead,
it need to be have a hook script configured to send email notifications.
See Chapter 5 of the SVN book for more information on hook scripts.

SVN does, however, provide a sample email notification hook script (written
in Perl) that you can use to get started with email notifications. You'll
find this script (called commit-email.pl) in the tool/hook-scripts
directory of the Subversion source.

-Bill

>
>
>Thank you
>
>Steven
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 25 00:31:46 2005

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

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