cvs-syncmail-talk Mailing List for syncmail (Page 17)

Brought to you by: bwarsaw, fdrake

cvs-syncmail-talk — User & developer discussions for the "syncmail" CVS checkin notification tool

You can subscribe to this list here.

2002	Jan	Feb	Mar (5)	Apr (5)	May (23)	Jun	Jul (11)	Aug (3)	Sep (1)	Oct (8)	Nov (24)	Dec (3)
2003	Jan (17)	Feb (5)	Mar (18)	Apr (10)	May (4)	Jun (5)	Jul (67)	Aug (7)	Sep (4)	Oct (2)	Nov (4)	Dec (9)
2004	Jan (16)	Feb (4)	Mar (7)	Apr (5)	May (4)	Jun (5)	Jul (3)	Aug (3)	Sep (3)	Oct (8)	Nov	Dec
2005	Jan (5)	Feb (6)	Mar (4)	Apr (1)	May (2)	Jun (2)	Jul (1)	Aug	Sep (5)	Oct (1)	Nov	Dec (7)
2006	Jan (10)	Feb (4)	Mar (10)	Apr (8)	May (8)	Jun (14)	Jul (7)	Aug (4)	Sep (4)	Oct (24)	Nov (29)	Dec (10)
2007	Jan (5)	Feb (12)	Mar (11)	Apr (10)	May (3)	Jun (3)	Jul (15)	Aug (28)	Sep (8)	Oct (5)	Nov (8)	Dec (13)
2008	Jan (7)	Feb (11)	Mar (29)	Apr (28)	May (17)	Jun (9)	Jul (18)	Aug (7)	Sep (8)	Oct (9)	Nov (11)	Dec (53)
2009	Jan (112)	Feb (19)	Mar (46)	Apr (32)	May (90)	Jun (91)	Jul (33)	Aug (11)	Sep (16)	Oct (23)	Nov (15)	Dec (3)
2010	Jan (1)	Feb	Mar (37)	Apr (47)	May (66)	Jun (69)	Jul (29)	Aug (45)	Sep (23)	Oct (3)	Nov (1)	Dec
2011	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov (1)	Dec
2012	Jan	Feb	Mar (2)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2013	Jan	Feb	Mar	Apr (1)	May (2)	Jun (1)	Jul (3)	Aug (6)	Sep (1)	Oct (7)	Nov (1)	Dec (1)
2014	Jan (1)	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep (1)	Oct	Nov	Dec (1)
2015	Jan (2)	Feb	Mar	Apr (1)	May	Jun	Jul	Aug (1)	Sep	Oct	Nov (1)	Dec (3)
2016	Jan (4)	Feb (5)	Mar (2)	Apr	May	Jun (2)	Jul (1)	Aug	Sep	Oct	Nov (2)	Dec (1)
2017	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (2)	Sep	Oct	Nov	Dec
2018	Jan	Feb (1)	Mar (25)	Apr (3)	May (1)	Jun (2)	Jul (2)	Aug	Sep	Oct	Nov (5)	Dec (1)
2019	Jan	Feb	Mar (1)	Apr (1)	May (1)	Jun (4)	Jul (3)	Aug	Sep (3)	Oct (6)	Nov (1)	Dec
2020	Jan	Feb	Mar	Apr	May	Jun (1)	Jul (1)	Aug (2)	Sep	Oct	Nov	Dec
2022	Jan	Feb (1)	Mar (1)	Apr (1)	May	Jun (1)	Jul	Aug	Sep	Oct	Nov (1)	Dec (1)
2023	Jan	Feb (1)	Mar (1)	Apr	May	Jun	Jul (1)	Aug	Sep (1)	Oct	Nov	Dec
2024	Jan (2)	Feb (2)	Mar (5)	Apr (2)	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec (1)
2025	Jan (1)	Feb	Mar	Apr	May	Jun	Jul (1)	Aug	Sep	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 15 16 17 18 19 .. 26 > >> (Page 17 of 26)

[Cvs-syncmail] 2003achievable

From: Rajendra Allen<cvs...@YA...> - 2003-12-27 07:11:00

<html><body bgcolor=#FFFFFF text=#000000>
.screeched.<font color=#000099><b>Have you been longing for a Designer Handbag,
Wallet, etc? But you don't want to spend the Big Bucks? Well, then here is the
place to be - A place where your dreams come true! Enjoy the Superior quality
and most affordable price and add a style to your life!<br>
</b></font><font color=#ffffff>exorcist.ii.aces</font><br>
<font color=#ff0000><b>Visit us at<a href=http://hot.4hoster.com/?11159901>CL1CK HER6</a></b><font color=#ffffff>crier.ethic.exemplifying</font>
<p><a href=http://hot.4hoster.com/lifehosteronline/remove>De1</a><font color=#ffffff>policies.boatswain.meal</font></p>
</font>
</body></html>

[Cvs-syncmail] [ cvs-syncmail-Bugs-865318 ] A common question!~~

From: SourceForge.net <no...@so...> - 2003-12-24 06:47:11

Bugs item #865318, was opened at 2003-12-24 14:47
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=865318&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: tao.lou (taolouis)
Assigned to: Nobody/Anonymous (nobody)
Summary: A common question!~~

Initial Comment:
Generating notification message...
Generating notification message... done.
[ronger@dniserver wwwroot]$ Traceback (most recent 
call last):
  File "/usr/local/dnicvs/CVSROOT/syncmail", line 322, in ?
    main()
  File "/usr/local/dnicvs/CVSROOT/syncmail", line 315, in 
main
    blast_mail(subject, people, specs[1:], contextlines, 
fromhost)
  File "/usr/local/dnicvs/CVSROOT/syncmail", line 221, in 
blast_mail
    conn.connect(MAILHOST, MAILPORT)
  File "/usr/lib/python2.2/smtplib.py", line 276, in connect
    for res in socket.getaddrinfo(host, port, 0, 
socket.SOCK_STREAM):
socket.gaierror: (-3, 'Temporary failure in name 
resolution')


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=865318&group_id=47611

[Cvs-syncmail] using the CVSROOT/users file for from address

From: Duane M. <du...@is...> - 2003-12-17 15:50:52

I like syncmail, but I'm having a problem I hope maybe has been resolved =
before.  I thought about modifying the script to do this myself, but I'm =
not that proficient in Python, so I thought I would see if what I want =
has already been done or considered on this list.
=20
I need the email sent by syncmail to come from the user's email address =
who is checking in the file.  This is so we can integrate with our JIRA =
issue/bug tracking system.  I have set up the CVSROOT/users file to map =
CVS user names to actual email addresses, but it appears as if syncmail =
is always using "cv...@cv...main" (for instance) as the SMTP =
return address.  My MTA keeps rejecting the email because it doesn't =
recognize the "cv...@cv...main" as a valid email address.  If I =
can get the return address to show up as val...@ou... =
(again, for example), the MTA will recognize it (and so will our =
issue-tracking system), but I can't seem to force syncmail to do this =
easily.

Any thoughts?

Many thanks,
Duane Moore
duane at iswsolutions dot com

[Cvs-syncmail] using the CVSROOT/users file for "From" address with syncmail

From: Duane M. <du...@is...> - 2003-12-15 20:40:54

I like syncmail, but I'm having a problem I hope maybe has been resolved =
before.  I thought about modifying the script to do this myself, but I'm =
not much of a Python person, so I thought I would see if what I want has =
already been done or considered.
=20
I need the email sent by syncmail to come from the user's email address =
who is checking in the file.  This is so we can integrate with our JIRA =
issue/bug tracking system.  I have set up the CVSROOT/users file to map =
CVS user names to actual email addresses, but it appears as if syncmail =
is always using "cv...@ho...main" (for instance) as the SMTP =
return address.  My MTA keeps rejecting the email because it doesn't =
recognize the "cv...@ho...main" as a valid email address.  If I =
can get the return address to show up as val...@ou... (again, =
for example), the MTA will recognize it, but I can't seem to force =
syncmail to do this easily.

Any thoughts?

Many thanks,
Duane Moore
duane at iswsolutions dot com

[Cvs-syncmail] Bug/patch: traceback when CVS/Entries missing

From: Greg W. <gw...@py...> - 2003-12-06 16:50:22

I've just noticed that syncmail bombs with an IOException trying to open
CVS/Entries when adding a directory to an otherwise-empty project.
See

  https://sourceforge.net/tracker/index.php?func=detail&aid=855359&group_id=47611&atid=450021

for details.  I included a patch that fixes the problem for me; it seems
pretty simple, but I'd like someone else (Fred?) to review it before I
check it in.

        Greg
-- 
Greg Ward <gw...@py...>                         http://www.gerg.ca/
Earn cash in your spare time -- blackmail your friends!

[Cvs-syncmail] [ cvs-syncmail-Patches-855359 ] Traceback opening Entries file for new dir in new project

From: SourceForge.net <no...@so...> - 2003-12-06 16:46:27

Patches item #855359, was opened at 2003-12-06 11:45
Message generated for change (Comment added) made by gward
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450021&aid=855359&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
>Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: Traceback opening Entries file for new dir in new project

Initial Comment:
Trying to add a new directory in a brand-new project fails.
Eg. in your $CVSHOME repository do this:
  mkdir test

Then go make a working copy somewhere:
  cvs -d /home/cvs co test

Add a new directory:
  mkdir foo
  cvs add foo

The "cvs add" succeeds, but syncmail bombs with

Traceback (most recent call last):
  File "/scratch/src/syncmail/syncmail", line 455, in ?
    main()
  File "/scratch/src/syncmail/syncmail", line 442, in main
    changes = load_change_info()
  File "/scratch/src/syncmail/syncmail", line 322, in
load_change_info
    f = open(entries_fn)
IOError: [Errno 2] No such file or directory: 'CVS/Entries'

BTW, this is with the latest trunk revision (1.36) of
syncmail;
I haven't tried the new-config branch.

The patch is trivial; I'll attach it, and if no one
objects, will
check it in.


----------------------------------------------------------------------

>Comment By: Greg Ward (gward)
Date: 2003-12-06 11:46

Message:
Logged In: YES 
user_id=14422

Fred, I'm assigning to you because you wrote the code that I'm
patching.  Also, you might want to merge this onto the
new-config
branch.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450021&aid=855359&group_id=47611

[Cvs-syncmail] [ cvs-syncmail-Patches-855359 ] Traceback opening Entries file for new dir in new project

From: SourceForge.net <no...@so...> - 2003-12-06 16:45:20

Patches item #855359, was opened at 2003-12-06 11:45
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450021&aid=855359&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Greg Ward (gward)
Assigned to: Nobody/Anonymous (nobody)
Summary: Traceback opening Entries file for new dir in new project

Initial Comment:
Trying to add a new directory in a brand-new project fails.
Eg. in your $CVSHOME repository do this:
  mkdir test

Then go make a working copy somewhere:
  cvs -d /home/cvs co test

Add a new directory:
  mkdir foo
  cvs add foo

The "cvs add" succeeds, but syncmail bombs with

Traceback (most recent call last):
  File "/scratch/src/syncmail/syncmail", line 455, in ?
    main()
  File "/scratch/src/syncmail/syncmail", line 442, in main
    changes = load_change_info()
  File "/scratch/src/syncmail/syncmail", line 322, in
load_change_info
    f = open(entries_fn)
IOError: [Errno 2] No such file or directory: 'CVS/Entries'

BTW, this is with the latest trunk revision (1.36) of
syncmail;
I haven't tried the new-config branch.

The patch is trivial; I'll attach it, and if no one
objects, will
check it in.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450021&aid=855359&group_id=47611

[Cvs-syncmail] [ cvs-syncmail-Bugs-845767 ] Syncmail script produces error

From: SourceForge.net <no...@so...> - 2003-11-30 09:27:19

Bugs item #845767, was opened at 2003-11-20 13:02
Message generated for change (Comment added) made by nuno-lopes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=845767&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Thorsten Kamann (thorque)
Assigned to: Nobody/Anonymous (nobody)
Summary: Syncmail script produces error

Initial Comment:
Hello SF-Support,

yesterday I setup the syncmail-script to report a
commit to a mailinglist for the project centaurus. This
function
properly...yesterday.
Since todays morning there occurs an error:

cvs -r ci -m
"/Centaurus/project/server/webapps/ROOT/index.htm"
  Checking in project/server/webapps/ROOT/index.htm;
 
/cvsroot/centaurus/project/server/webapps/ROOT/index.htm,v
 <--  index.htm
  new revision: 1.2; previous revision: 1.1
  done
  Mailing cen...@li......
  Generating notification message...
  Generating notification message... done.
  Mailing cen...@li......
  Generating notification message...
  Traceback (innermost last):
    File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail",
line 322, in ?
      main()
    File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail",
line 315, in main
      blast_mail(subject, people, specs[1:],
contextlines, fromhost)
    File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail",
line 240, in blast_mail
      print calculate_diff(file, contextlines)
    File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail",
line 139, in calculate_diff
      file, oldrev, newrev = string.split(filespec, ',')
  ValueError: unpack list of wrong size

I'm using the Eclipse IDE Version 1.2 on SuSE Linux 8.2
Whats wrong?

Best regards 
Thorsten Kamann

----------------------------------------------------------------------

Comment By: Nuno Lopes (nuno-lopes)
Date: 2003-11-30 09:27

Message:
Logged In: YES 
user_id=841194

Hi,

Syncmail used to work, but today I imported a new 
module to the cvs repository and it gave me an error:

------------
No conflicts created by this import

Mailing php...@li......
Generating notification message...
Generating notification message... done.
Mailing php...@li......
Generating notification message...
Traceback (innermost last):
  File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail", 
line 322, in ?
    main()
  File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail", 
line 315, in main
    blast_mail(subject, people, specs[1:], contextlines, 
fromhost)
  File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail", 
line 240, in blast_mail
    print calculate_diff(file, contextlines)
  File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail", 
line 139, in calculate_dif
f
    file, oldrev, newrev = string.split(filespec, ',')
ValueError: unpack list of wrong size
----------------------

I didn't receive any e-mail for this import.

Nuno Lopes

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=845767&group_id=47611

[Cvs-syncmail] [ cvs-syncmail-Bugs-850695 ] Using syncmail with %s fails

From: SourceForge.net <no...@so...> - 2003-11-28 11:24:23

Bugs item #850695, was opened at 2003-11-28 12:24
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=850695&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Gert-Jan Paulissen (gpaulissen)
Assigned to: Nobody/Anonymous (nobody)
Summary: Using syncmail with %s fails

Initial Comment:
In my loginfo script the following line has been added:

DEFAULT /cvsroot/sitedocs/CVSROOT/cvstools/syncmail 
%s gpa...@us...

The default %{sVv} has not been used because it 
generated too much lines for binary files. But this works 
neither:

Traceback (innermost last):
  File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail", 
line 322, in ?
    main()
  File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail", 
line 315, in main
    blast_mail(subject, people, specs[1:], contextlines, 
fromhost)
  File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail", 
line 240, in blast_mail
    print calculate_diff(file, contextlines)
  File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail", 
line 139, in calculate_diff
    file, oldrev, newrev = string.split(filespec, ',')
ValueError: unpack list of wrong size

Apparently the code assumes several options should be 
specified.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=850695&group_id=47611

[Cvs-syncmail] [ cvs-syncmail-Bugs-845767 ] Syncmail script produces error

From: SourceForge.net <no...@so...> - 2003-11-20 13:03:02

Bugs item #845767, was opened at 2003-11-20 14:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=845767&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Thorsten Kamann (thorque)
Assigned to: Nobody/Anonymous (nobody)
Summary: Syncmail script produces error

Initial Comment:
Hello SF-Support,

yesterday I setup the syncmail-script to report a
commit to a mailinglist for the project centaurus. This
function
properly...yesterday.
Since todays morning there occurs an error:

cvs -r ci -m
"/Centaurus/project/server/webapps/ROOT/index.htm"
  Checking in project/server/webapps/ROOT/index.htm;
 
/cvsroot/centaurus/project/server/webapps/ROOT/index.htm,v
 <--  index.htm
  new revision: 1.2; previous revision: 1.1
  done
  Mailing cen...@li......
  Generating notification message...
  Generating notification message... done.
  Mailing cen...@li......
  Generating notification message...
  Traceback (innermost last):
    File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail",
line 322, in ?
      main()
    File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail",
line 315, in main
      blast_mail(subject, people, specs[1:],
contextlines, fromhost)
    File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail",
line 240, in blast_mail
      print calculate_diff(file, contextlines)
    File "/cvsroot/sitedocs/CVSROOT/cvstools/syncmail",
line 139, in calculate_diff
      file, oldrev, newrev = string.split(filespec, ',')
  ValueError: unpack list of wrong size

I'm using the Eclipse IDE Version 1.2 on SuSE Linux 8.2
Whats wrong?

Best regards 
Thorsten Kamann

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=845767&group_id=47611

[Cvs-syncmail] [ cvs-syncmail-Bugs-841623 ] rcsdiff troubles?

From: SourceForge.net <no...@so...> - 2003-11-13 18:50:34

Bugs item #841623, was opened at 2003-11-13 19:50
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=841623&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Joachim Pileborg (arrow)
Assigned to: Nobody/Anonymous (nobody)
Summary: rcsdiff troubles?

Initial Comment:
When doing a cvs commit, I get rcsdiff errors:

Checking in kernel/class.c;
/cvsroot/evilos-kernel/evilos/kernel/class.c,v  <-- 
class.c
new revision: 1.3; previous revision: 1.2
done
Mailing ar...@us......
Generating notification message...
Generating notification message... done.
rcsdiff: RCS/1.2,v: No such file or directory
rcsdiff: -r option is ignored after pathnames
rcsdiff: RCS/1.3,v: No such file or directory
rcsdiff:
/cvsroot/evilos-kernel/evilos/kernel/Attic/RCS/class.c,v:
No such file or directory


My $CVSROOT/CVSROOT/loginfo entry looks like this:
evilos $CVSROOT/CVSROOT/syncmail %s
ar...@us...


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=841623&group_id=47611

[Cvs-syncmail] problem finding interpreter

From: Pedro A. <ped...@po...> - 2003-10-16 19:02:14

I have a problem running syncmail from cvs of 2003-10-16

I checked out this version because version 1.0 was not working so I 
thought I would give a try to the HEAD version.

I don't really understand but the problem is that everytime I try to run 
the script, it complains like this:

[root@server pedro]# /usr/local/bin/syncmail
: bad interpreter: No such file or directoryon

[root@server pedro]# which python
/usr/bin/python

Header of syncmail:
#! /usr/bin/python
...
...

If I run
[root@server pedro]# python /usr/local/bin/syncmail
Complicated notification for CVS checkins.
...
...

Then it runs ok.

Why is this?
I don't know how to run "python /usr/local/bin/syncmail" in loginfo 
file. It doesn't work...

[Cvs-syncmail] confused about file xxx -- ignoring

From: xavier <lis...@na...> - 2003-09-26 14:45:08

Hi,

is there something wrong with my setup ?

cvs-syncmail is always printing this
"confused about file xxx -- ignoring"
when i commit a file, and there are other files in the directory
but not commited...

i do cvs ci -m 'n' in the directory.

using debian version 1.2+cvs.2003.07.28-2

thanks


-- 
xavier

[Cvs-syncmail] crossovers

From: Kennedy<cvs...@AO...> - 2003-09-12 09:34:18

<html>
<body><font color="#ffffff">sashay <font color="#ffffff">bertrand <font color="#ffffff">achieves <font color="#ffffff">imaging <font color="#ffffff">sanguinary <font color="#ffffff">powerlessness <font color="#ffffff">powerless <font color="#ffffff">imitating <font color="#ffffff">boatmen <font color="#ffffff">scrawls <font color="#ffffff">tea <font color="#ffffff">plums <font color="#ffffff">milestone <font color="#ffffff">medieval <font color="#ffffff">humaneness <font color="#ffffff">pool <font color="#ffffff">midland <font color="#ffffff">exert <font color="#ffffff">meander <font color="#ffffff">executor <font color="#ffffff">boil <font color="#ffffff">scopes <font color="#ffffff">hydroxylate <font color="#ffffff">admissible <font color="#ffffff">melange <font color="#ffffff">counterattack <font color="#ffffff">tapestry <font color="#ffffff">postpaid <font color="#ffffff">athenian <font color="#ffffff">medium <font color="#ffffff">$RANDO
MIZE <font color="#ffffff">mighty <font color="#ffffff">adoptive <font color="#ffffff">tester <font color="#ffffff">arpa <font color="#ffffff">satchel <font color="#ffffff">explanations <font color="#ffffff">taut <font color="#ffffff">boldly <font color="#ffffff">creed <font color="#ffffff">adaptors <font color="#ffffff">playoff <font color="#ffffff">scaring <font color="#ffffff">creations <font color="#ffffff">bouquets <font color="#ffffff">tansy <font color="#ffffff">methodist <font color="#ffffff">exponentiates <font color="#ffffff">mayhap <font color="#ffffff">bernard <font color="#ffffff">housewares <font color="#ffffff">hounds <font color="#ffffff">hummed <font color="#ffffff">acquiesces <font color="#ffffff">taxonomic <font color="#ffffff">hornwort <font color="#ffffff">pluton <font color="#ffffff">azerbaijan <font color="#ffffff">humidifiers <font color="#ffffff">becker <font color="#ffffff">matrimonial <font color="#ffffff">$RANDOM
IZE <font color="#ffffff">microseconds <font color="#ffffff">melted <font color="#ffffff">bootlegger <font color="#ffffff">couscous <font color="#ffffff">taped <font color="#ffffff">bodyweight <font color="#ffffff">courteously <font color="#ffffff">technique <font color="#ffffff">adjudging <font color="#ffffff">politer <font color="#ffffff">benedikt <font color="#ffffff">mediates <font color="#ffffff">mike ames bissau asher medics illogic expenditure posthumous hustled<p>
<a href="http://srd.yahoo.com/drst/counterintuitive/*http://www.med12z.com/sh/index.html"> 
<img border="0" 
 src="http://srd.yahoo.com/drst/blushing/*http://www.8867v.com/file/ra.gif" >
</a>
 </p><font color="#ffffff">exam <font color="#ffffff">mi <font color="#ffffff">pleasing <font color="#ffffff">scratches <font color="#ffffff">porosity <font color="#ffffff">accountability <font color="#ffffff">european <font color="#ffffff">messed <font color="#ffffff">terrorists <font color="#ffffff">credibility <font color="#ffffff">beaujolais <font color="#ffffff">ares <font color="#ffffff">expressible <font color="#ffffff">antietam <font color="#ffffff">merchant <font color="#ffffff">militate <font color="#ffffff">exploited <font color="#ffffff">advanced <font color="#ffffff">search <font color="#ffffff">temples <font color="#ffffff">angus <font color="#ffffff">millinery <font color="#ffffff">menu <font color="#ffffff">medicine <font color="#ffffff">cos <font color="#ffffff">countenance <font color="#ffffff">blunting <font color="#ffffff">antonio <font color="#ffffff">sands <font color="#ffffff">boastful <font color="#ffffff">$RANDOM
IZE <font color="#ffffff">polluting <font color="#ffffff">hysterically <font color="#ffffff">adrift <font color="#ffffff">adjuncts <font color="#ffffff">exists <font color="#ffffff">scalable <font color="#ffffff">cosmology <font color="#ffffff">iliac <font color="#ffffff">branchings <font color="#ffffff">portly <font color="#ffffff">exclaiming <font color="#ffffff">pouts <font color="#ffffff">berlitz <font color="#ffffff">humbler <font color="#ffffff">eventfully <font color="#ffffff">target <font color="#ffffff">miles <font color="#ffffff">couches <font color="#ffffff">bookkeeping <font color="#ffffff">powders <font color="#ffffff">identically <font color="#ffffff">methacrylate <font color="#ffffff">telescopes <font color="#ffffff">accumulators <font color="#ffffff">mechanist <font color="#ffffff">beijing <font color="#ffffff">meddler <font color="#ffffff">plyscore <font color="#ffffff">acuity <font color="#ffffff">bower <font color="#ffffff">$RANDOMI
ZE <font color="#ffffff">exploded <font color="#ffffff">bondage <font color="#ffffff">accusingly <font color="#ffffff">advertisements <font color="#ffffff">teamster <font color="#ffffff">accuser <font color="#ffffff">exert <font color="#ffffff">exclaimer <font color="#ffffff">exhibit <font color="#ffffff">anna <font color="#ffffff">tapers <font color="#ffffff">coupon <font color="#ffffff">RANDOMIZE illness bertha adamson hopefully postprocess adjudge powered howls</body>
</html>

[Cvs-syncmail] Bug#205593: cvs-syncmail: man page misleading : %{sVv} or %{sSv} ?

From: Kevin R. <ke...@ro...> - 2003-08-15 20:26:31

Hello Syncmail guys,

I'm forwarding this report from a Debian user.

Thanks!

Kevin

xavier renaut wrote:
> Package: cvs-syncmail
> Version: 1.2+cvs.2003.07.28-1
> Severity: normal
> 
> the man page provide exemples with %{sVv}
> and explain things about %{sSv}...
> (Note that %{sSv} is magic that CVS understands and replaces with
> information...)
> 
> 
> there would be a need for an explanation about  %{sVv}
> 
> thanks
> 
> Debian Release: testing/unstable
> Architecture: i386
> Kernel: Linux natch.8d.com 2.4.21natch #2 Wed Jul 16 13:39:23 EDT 2003 i686
> Locale: LANG=C, LC_CTYPE=en_US
> 
> Versions of packages cvs-syncmail depends on:
> ii  python                        2.2.3-3    An interactive high-level object-o
> 
>

[Cvs-syncmail] [ cvs-syncmail-Bugs-789410 ] Fix usage description

From: SourceForge.net <no...@so...> - 2003-08-15 18:42:41

Bugs item #789410, was opened at 2003-08-15 11:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=789410&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix usage description

Initial Comment:
The syntax of syncmail when using syncmail --help is
incorrect. 

If we use ./syncmail [options] <%S> email-addr
[email-addr..], the collect_diff will fail because it
expects the previous and the new version of the file.
Correct usage should read:  ./syncmail [options] %{sVv}
email-addr [email-addr..].

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=789410&group_id=47611

[Cvs-syncmail] syncmail branchctl,1.3,1.4

From: Fred L. D. <fd...@us...> - 2003-08-07 16:41:30

Update of /cvsroot/cvs-syncmail/syncmail
In directory sc8-pr-cvs1:/tmp/cvs-serv17596

Modified Files:
	branchctl 
Log Message:
add ability to present a useful message for closed branches


Index: branchctl
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/branchctl,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- branchctl	14 Jul 2003 18:11:47 -0000	1.3
+++ branchctl	7 Aug 2003 16:41:27 -0000	1.4
@@ -70,6 +70,7 @@
 DEFAULT_CONFIGURATION = {
     "verbose": "true",
     "open": "true",
+    "closed-message": "",
     "cross-branch-commits": "true",
     }
 
@@ -335,6 +336,7 @@
         OptionsBase.__init__(self, config, args)
 
         self.open = config.getbool("open")
+        self.closed_message = config.get("closed-message")
         self.cross_commits = config.getbool("cross-branch-commits")
 
 def load_cmdline(args):
@@ -387,7 +389,11 @@
             if not denied:
                 denied = 1
                 print
-            print branchname, "is closed"
+            why = config.closed_message
+            if why:
+                print branchname, "is closed:", why
+            else:
+                print branchname, "is closed"
         if crossed_branches and not config.cross_commits:
             if not denied:
                 denied = 1

[Cvs-syncmail] Re: New script -- branchctl

From: Fred L. D. Jr. <fd...@ac...> - 2003-08-06 18:18:28

Fred L. Drake, Jr. writes:
 > I've just added a new script to the cvs-syncmail CVS trunk: branchctl.
 > This script controls the use of branches within a CVS repository.

So far, no one has commented on this at all.  Has anyone used it?
Does anyone expect to?

For most projects, with only a few branches and few developers, this
probably isn't very valuable, but I think it's useful when large
numbers of developers are involved and many branches are in the
repository.

Are there missing features that would make this more useful for
others?

  -Fred

-- 
Fred L. Drake, Jr.  <fdrake at acm.org>
PythonLabs at Zope Corporation

[Cvs-syncmail] cvs-syncmail-talk,Get paid for your opinions plus holiday offer...

From: mcdonald <lam...@ms...> - 2003-08-04 21:04:37

VG86IGN2cy1zeW5jbWFpbC10YWxrQGxpc3RzLnNvdXJjZWZvcmdlLm5ldA0KDQo8aHRtbD4NCg0K
PGhlYWQ+DQoNCjx0aXRsZT53d3cucGFpZHN1cnZleXNvbmxpbmUuY29tPC90aXRsZT4NCg0KPC9o
ZWFkPg0KDQo8Ym9keT4NCg0KPHRhYmxlIGJvcmRlcj0iMCIgd2lkdGg9IjYwJSIgY2VsbHNwYWNp
bmc9IjAiIGNlbGxwYWRkaW5nPSIwIiBoZWlnaHQ9IjI3MiI+DQoNCjx0cj4NCg0KPHRkIHdpZHRo
PSIxMDAlIiBoZWlnaHQ9IjI3MiI+PGEgaHJlZj0iaHR0cDovL2hvcC5jbGlja2JhbmsubmV0Lz9z
dXJ2dG9kYXkvc3VydmV5czIiPjxpbWcNCg0Kc3JjPSJodHRwOi8vd3d3LnBhaWRzdXJ2ZXlzb25s
aW5lLmNvbS90b3AuZ2lmIiB3aWR0aD0iNDM2IiBoZWlnaHQ9IjUwIg0KDQphbHQ9Imh0dHA6Ly93
d3cucGFpZHN1cnZleXNvbmxpbmUuY29tL3RvcC5naWYgKDI2NTkgYnl0ZXMpIiBib3JkZXI9IjAi
PjwvYT48YnI+DQoNCjxhIGhyZWY9Imh0dHA6Ly9ob3AuY2xpY2tiYW5rLm5ldC8/c3VydnRvZGF5
L3N1cnZleXMyIj48aW1nDQoNCnNyYz0iaHR0cDovL3d3dy5wYWlkc3VydmV5c29ubGluZS5jb20v
bWlkZGxlLmpwZyIgd2lkdGg9IjQzNiIgaGVpZ2h0PSIxNDkiDQoNCmFsdD0iaHR0cDovL3d3dy5w
YWlkc3VydmV5c29ubGluZS5jb20vbWlkZGxlLmpwZyAoMTU4MTUgYnl0ZXMpIiBib3JkZXI9IjAi
PjwvYT48YnI+DQoNCjxhIGhyZWY9Imh0dHA6Ly9ob3AuY2xpY2tiYW5rLm5ldC8/c3VydnRvZGF5
L3N1cnZleXMyIj48aW1nDQoNCnNyYz0iaHR0cDovL3d3dy5wYWlkc3VydmV5c29ubGluZS5jb20v
Ym90dG9tLmdpZiIgd2lkdGg9IjQzNiIgaGVpZ2h0PSI4NyINCg0KYWx0PSJodHRwOi8vd3d3LnBh
aWRzdXJ2ZXlzb25saW5lLmNvbS9ib3R0b20uZ2lmICg1NTE3IGJ5dGVzKSIgYm9yZGVyPSIwIj48
L2E+PC90ZD4NCg0KPC90cj4NCg0KPC90YWJsZT4NCg0KPC9ib2R5Pg0KDQo8L2h0bWw+DQoNCg0K
DQoNCg0KVG8gYmUgcmVtb3ZlZCBmcm9tIG91ciBsaXN0OiAgUmVwbHkgYmFjayB0bzogZ3JhbmRv
ZmVyc0Bsb3dwcmljZXBsYXRpbnVtLmNvbT9zdWJqZWN0PU5vVGhhbmtz

[Cvs-syncmail] =?GB2312?B?1f64rtH7x+u6rw==?=

From: <it...@it...> - 2003-07-30 19:47:42

尊敬的各位朋友：


    山东省是中国经济最发达的地区，也是最大的IT产品市

场之一，每年有1000亿元的市场采购，是中国北方地区最大

（北京除外）的区域市场。

      为了发展你们的事业，获得更多的市场机会，我们

热情邀请您参加'2003中国国际信息技术博览会暨城市信息

化市长论坛。

    中国国际信息技术博览会（ITEXPO）是山东省规模最大、

效果最好，也是唯一由政府主办和承办的IT盛会。该会以观

众层次高、展览效果好、服务体贴周到而闻名遐迩，成为众

多IT企业进军齐鲁大地的首要选择。IBM、CISCO、HP、MICROSOFT、

西门子、爱立信、诺基亚等世界著名IT跨国集团和华为、联

想、方正、神州数码、浪潮等国内IT知名企业均通过参加展

览，顺利打开山东市场。ITEXPO自从1999年开展以来，已经

有70万观众参观，达成交易上百亿元。

    2003年山东省各行业、各部门、各企业全面加大信息化

投资力度，并在本届展会上选择合作单位，请抓住这个宝贵

的机会，到济南开辟更大的事业！





                          中国国际信息技术博览会  诚邀


                              2003、7、28


时间： 2003年10月16日――10月19日（周四--周日）
 
大会组委会设在济南市人民政府信息化办公室

地址：[250001]济南市纬二路182号

济南市人民政府信息化办公室

电话：86-531-2075611

传真：86-531-2075606

手机：13505410459

联系人：路晨曦

由于展位特别紧张，请火速预订。详细资料可来电索取。

http://www.ITexpo.com.cn

http://www.jn.gov.cn

mailto:it...@jn...

[Cvs-syncmail] syncmail/doc branchctl.1,NONE,1.1 branchctl.sgml,NONE,1.1

From: Fred L. D. <fd...@us...> - 2003-07-21 18:09:14

Update of /cvsroot/cvs-syncmail/syncmail/doc
In directory sc8-pr-cvs1:/tmp/cvs-serv2203

Added Files:
	branchctl.1 branchctl.sgml 
Log Message:
Manual page for branchctl.

--- NEW FILE: branchctl.1 ---
.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <st...@gg...>.
.TH "BRANCHCTL" "1" "21 July 2003" "" ""

.SH NAME
branchctl \- Control access to CVS repositories by branch
.SH SYNOPSIS

\fBbranchctl\fR [ \fB--config \fIfile\fB\fR ] [ \fB--no-config\fR ] [ \fB--cvsroot \fIpath\fB\fR ] [ \fB--help | -h\fR ]

.SH "DESCRIPTION"
.PP
\fBbranchctl\fR takes care of disallowing
checkins for branches that have been marked "off-limits".
.PP
In any large project using CVS branches, some branches will be
active, some will have been merged into other branches or the
trunk, and others will have been bypassed.  CVS really does not
provide tools to make easy to determine which branches are still
being used, and it's easy for someone new to a project to find
an interesting tangent in a branch and start working on it, even
though the branch has been abandoned or has already been merged
into another branch where the features of the original branch
are to be maintained.
.PP
CVS also allows a single commit to affect files on more than one
branch; this is possible by committing two files in one working
directory after using \fBcvs up -r\fR to move one
of them to a different branch.  \fBbranchctl\fR
allows the repository administrator to disallow such commits.
.PP
branchctl works by integrating with CVS in the repository
using the configuration files in the repository's CVSROOT
module.  When CVS executes commands from the
\fIcommitinfo\fR file, branchctl is invoked if
it has been configured.
.SH "SETTING UP BRANCHCTL"
.PP
Setting up branchctl is not difficult, but there are usually
several steps:
.TP 3
1. 
Install branchctl.  This is usually done by adding it to
your CVS repository, but it may be located in a directory on
the default \fBPATH\fR, or just about anywhere else.
.TP 3
2. 
Configure CVS to invoke branchctl.  This is a matter of
adding and/or changing some of the configuration files in
the CVSROOT module in the repository.
.SS "INSTALL BRANCHCTL"
.PP
branchctl consists of a single Python script; it does not
need any supplemental data files.  There are two approaches to
installing the script:
check it into the repository, or place it in a shared location on the CVS
server.
.PP
To install branchctl by checking it into the repository
itself, check out a working copy of the CVSROOT module.  Add
the name branchctl to the file
\fIcheckoutlist\fR in that directory as well,
and commit that change.  This will cause a copy of branchctl
to be checked out into the repository itself.  Copy te
branchctl script into the directory, make sure that it is
executable by everyone (you should use \fBchmod a+x
branchctl\fR for this), and use the \fBcvs
add\fR and \fBcvs commit\fR commands to
add it to the repository.  Once the commit is complete, a
checked-out copy of the branchctl script should be located
in the repository in the \fICVSROOT\fR directory in the
repository.  This is the usual way of integrating branchctl
into a CVS repository.
.PP
To install branchctl outside of the repository, find a
location for the script.  This can be in a "bin" directory
such as \fI/usr/local/bin/\fR, or can be in
some other location.  The only requirement is that all users
of the repository be able to execute the script (you should
use \fBchmod a+x branchctl\fR for this).  This
approach requires direct access to the CVS server machine, and
is most useful if several repositories are going to share a
single copy of branchctl (maybe to ensure the same version
is used for each; it's not large enough for disk space to be
an issue).
.SS "CONFIGURE CVS TO USE BRANCHCTL"
.PP
Getting the CVS server to invoke branchctl requires editing
one more file in the \fICVSROOT\fR module of the repository.
Even if you're using a shared installation of branchctl,
this configuration needs to be performed for each repository.
.PP
The \fIcommitinfo\fR file in the \fICVSROOT\fR module needs to be
modified to invoke branchctl when appropriate.  Just when is
appropriate depends entirely on your project.  If your
\fIcommitinfo\fR file still contains the
comments that \fBcvs init\fR copies in, this is a
good time to read them if you haven't.  If the file does not
already contain any configuration lines, you can simply add to
the end of the file.
.PP
Here are some example lines to get you started:

.nf
DEFAULT $CVSROOT/CVSROOT/branchctl

ProjectOne $CVSROOT/CVSROOT/branchctl --no-config

ProjectTwo $CVSROOT/CVSROOT/branchctl --config project-two.conf
.fi
.PP
The first line causes the default configuration file,
\fIbranchctl.conf\fR, to be used everywhere
that doesn't use an alternate invocation of branchctl.
.PP
The second line tells CVS to use branchctl's internal
configuration defaults instead of reading a configuration
file, but to only do so in the the \fIProjectOne\fR directory of the
repository.
.PP
The third line tells CVS to run branchctl using a separate
configuration file for the \fIProjectTwo\fR directory in the
repository.
.PP
To finish the repository configuration, commit the changes
you've made.  Once the CVS server has reported that it is
"Rebuilding administrative file database", your repository is
configured to use branchctl.
.SH "OPTIONS"
.PP
When an option includes an argument, you may specify the
argument either separate ("-d output") or mashed ("-doutput").
branchctl supports both.  For long options which include an
argument, the argument may be separated from the option
("--fromhost example.com") or mashed, but with an equals sign
between the option and the argument ("--fromhost=example.com").
.TP
\fB--config \fIfile\fB\fR
Use \fIfile\fR as the configuration
file for branchctl.  By default, a file named
\fIbranchctl.conf\fR is used if it exists.
If the name of the configuration file is relative, it is
interpreted as relative to the \fICVSROOT\fR administrative
directory of the repository.  \fB--config\fR is
incompatible with \fB--no-config\fR.
.TP
\fB--no-config\fR
Do not use a configuration file for branchctl.  This can
be used to disable the use of the default configuration
file.  \fB--no-config\fR is incompatible with
\fB--config\fR.  Note that it's not normally
useful to specify this option, but it may be useful when
you want to allow changes to any branch within a single
CVS module, but use a more sophisticated configuration for
the rest of the repository.
.TP
\fB--cvsroot \fIpath\fB\fR
Use \fIpath\fR as the value for the
\fBCVSROOT\fR environment variable.  This is
usually not needed.
.TP
\fB--help\fR
.TP
\fB-h\fR
Print a summary of the command line options to standard
output.
.SH "BUGS"
.PP
There are probably some bugs.  If you find them, please
report them to the maintainers using the bug
tracker <URL:http://sourceforge.net/projects/cvs-syncmail/>.
.SH "SEE ALSO"
.PP
The branchctl page <URL:http://sourceforge.net/projects/cvs-syncmail/> on SourceForge <URL:http://sourceforge.net/>.
.PP
The CVS home page <URL:http://www.cvshome.org/>.
.SH "AUTHOR"
.PP
branchctl was originally written by Fred Drake.
.PP
This manual page was written by Fred L. Drake, Jr. <fd...@ac...>.

--- NEW FILE: branchctl.sgml ---
<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [

<!-- Process this file with docbook-to-man to generate an nroff manual
     page: `docbook-to-man manpage.sgml > manpage.1'.  You may view
     the manual page with: `docbook-to-man manpage.sgml | nroff -man |
     less'.  A typical entry in a Makefile or Makefile.am is:

manpage.1: manpage.sgml
	docbook-to-man $< > $@
  -->

  <!-- Fill in your name for FIRSTNAME and SURNAME. -->
  <!ENTITY dhfirstname "<firstname>Fred</firstname>">
  <!ENTITY dhsurname   "<surname>Drake</surname>">
  <!-- Please adjust the date whenever revising the manpage. -->
  <!ENTITY dhdate      "<date>July 14, 2003</date>">
  <!-- SECTION should be 1-8, maybe w/ subsection other parameters are
       allowed: see man(7), man(1). -->
  <!ENTITY dhsection   "<manvolnum>1</manvolnum>">
  <!ENTITY dhemail     "<email>fd...@ac...</email>">
  <!ENTITY dhusername  "Fred L. Drake, Jr.">
  <!ENTITY dhucpackage "<refentrytitle>branchctl</refentrytitle>">
  <!ENTITY dhpackage   "branchctl">

  <!ENTITY debian      "<productname>Debian GNU/Linux</productname>">
  <!ENTITY gnu         "<acronym>GNU</acronym>">
  <!ENTITY sourceforge "<ulink url='http://sourceforge.net/'>SourceForge</ulink>">
]>
<refentry>
  <refentryinfo>
    <address>
      &dhemail;
    </address>
    <author>
      &dhfirstname;
      &dhsurname;
    </author>
    <copyright>
      <year>2003</year>
      <holder>&dhusername;</holder>
    </copyright>
    &dhdate;
  </refentryinfo>
  <refmeta>
    &dhucpackage;
    &dhsection;
  </refmeta>
  <refnamediv>
    <refname>&dhpackage;</refname>
    <refpurpose>Control access to CVS repositories by branch</refpurpose>
  </refnamediv>
  <refsynopsisdiv>
    <cmdsynopsis>
      <command>&dhpackage;</command>
      <arg>--config <replaceable>file</replaceable></arg>
      <arg>--no-config</arg>
      <arg>--cvsroot <replaceable>path</replaceable></arg>
      <arg><option>--help</option> | <option>-h</option></arg>
    </cmdsynopsis>
  </refsynopsisdiv>

  <refsect1>
    <title>Description</title>
    <para>
      <command>&dhpackage;</command> takes care of disallowing
      checkins for branches that have been marked "off-limits".
    </para>
    <para>
      In any large project using CVS branches, some branches will be
      active, some will have been merged into other branches or the
      trunk, and others will have been bypassed.  CVS really does not
      provide tools to make easy to determine which branches are still
      being used, and it's easy for someone new to a project to find
      an interesting tangent in a branch and start working on it, even
      though the branch has been abandoned or has already been merged
      into another branch where the features of the original branch
      are to be maintained.
    </para>
    <para>
      CVS also allows a single commit to affect files on more than one
      branch; this is possible by committing two files in one working
      directory after using <command>cvs up -r</command> to move one
      of them to a different branch.  <command>&dhpackage;</command>
      allows the repository administrator to disallow such commits.
    </para>
    <para>
      &dhpackage; works by integrating with CVS in the repository
      using the configuration files in the repository's CVSROOT
      module.  When CVS executes commands from the
      <filename>commitinfo</filename> file, &dhpackage; is invoked if
      it has been configured.
    </para>
  </refsect1>

  <refsect1>
    <title>Setting Up branchctl</title>
    <para>
      Setting up &dhpackage; is not difficult, but there are usually
      several steps:
    </para>
    <orderedlist numeration="arabic">
      <listitem>
        <para>
          Install &dhpackage;.  This is usually done by adding it to
          your CVS repository, but it may be located in a directory on
          the default <envar>PATH</envar>, or just about anywhere else.
        </para>
      </listitem>
      <listitem>
        <para>
          Configure CVS to invoke &dhpackage;.  This is a matter of
          adding and/or changing some of the configuration files in
          the CVSROOT module in the repository.
        </para>
      </listitem>
    </orderedlist>

    <refsect2>
      <title>Install &dhpackage;</title>
      <para>
        &dhpackage; consists of a single Python script; it does not
        need any supplemental data files.  There are two approaches to
        installing the script:
        <simplelist type="inline">
          <member>check it into the repository</member>
          <member>or place it in a shared location on the CVS
          server</member>
        </simplelist>.
      </para>
      <para>
        To install &dhpackage; by checking it into the repository
        itself, check out a working copy of the CVSROOT module.  Add
        the name <literal>&dhpackage;</literal> to the file
        <filename>checkoutlist</filename> in that directory as well,
        and commit that change.  This will cause a copy of &dhpackage;
        to be checked out into the repository itself.  Copy te
        &dhpackage; script into the directory, make sure that it is
        executable by everyone (you should use <command>chmod a+x
        &dhpackage;</command> for this), and use the <command>cvs
        add</command> and <command>cvs commit</command> commands to
        add it to the repository.  Once the commit is complete, a
        checked-out copy of the &dhpackage; script should be located
        in the repository in the <filename
        class="directory">CVSROOT</filename> directory in the
        repository.  This is the usual way of integrating &dhpackage;
        into a CVS repository.
      </para>
      <para>
        To install &dhpackage; outside of the repository, find a
        location for the script.  This can be in a "bin" directory
        such as <filename
        class="directory">/usr/local/bin/</filename>, or can be in
        some other location.  The only requirement is that all users
        of the repository be able to execute the script (you should
        use <command>chmod a+x &dhpackage;</command> for this).  This
        approach requires direct access to the CVS server machine, and
        is most useful if several repositories are going to share a
        single copy of &dhpackage; (maybe to ensure the same version
        is used for each; it's not large enough for disk space to be
        an issue).
      </para>
    </refsect2>

    <refsect2>
      <title>Configure CVS to use &dhpackage;</title>
      <para>
        Getting the CVS server to invoke &dhpackage; requires editing
        one more file in the <filename
        class="directory">CVSROOT</filename> module of the repository.
        Even if you're using a shared installation of &dhpackage;,
        this configuration needs to be performed for each repository.
      </para>
      <para>
        The <filename>commitinfo</filename> file in the <filename
        class="directory">CVSROOT</filename> module needs to be
        modified to invoke &dhpackage; when appropriate.  Just when is
        appropriate depends entirely on your project.  If your
        <filename>commitinfo</filename> file still contains the
        comments that <command>cvs init</command> copies in, this is a
        good time to read them if you haven't.  If the file does not
        already contain any configuration lines, you can simply add to
        the end of the file.
      </para>
      <para>
        Here are some example lines to get you started:
<literallayout>
DEFAULT $CVSROOT/CVSROOT/branchctl

ProjectOne $CVSROOT/CVSROOT/branchctl --no-config

ProjectTwo $CVSROOT/CVSROOT/branchctl --config project-two.conf
</literallayout>
      </para>
      <para>
        The first line causes the default configuration file,
        <filename>&dhpackage;.conf</filename>, to be used everywhere
        that doesn't use an alternate invocation of &dhpackage;.
      </para>
      <para>
        The second line tells CVS to use &dhpackage;'s internal
        configuration defaults instead of reading a configuration
        file, but to only do so in the the <filename
        class="directory">ProjectOne</filename> directory of the
        repository.
      </para>
      <para>
        The third line tells CVS to run &dhpackage; using a separate
        configuration file for the <filename
        class="directory">ProjectTwo</filename> directory in the
        repository.
      </para>
      <para>
        To finish the repository configuration, commit the changes
        you've made.  Once the CVS server has reported that it is
        "Rebuilding administrative file database", your repository is
        configured to use &dhpackage;.
      </para>
    </refsect2>
  </refsect1>

  <refsect1>
    <title>Options</title>
    <para>
      When an option includes an argument, you may specify the
      argument either separate ("-d output") or mashed ("-doutput").
      &dhpackage; supports both.  For long options which include an
      argument, the argument may be separated from the option
      ("--fromhost example.com") or mashed, but with an equals sign
      between the option and the argument ("--fromhost=example.com").
    </para>

    <variablelist>
      <varlistentry>
        <term><option>--config <replaceable>file</replaceable></option></term>
        <listitem>
          <para>
            Use <replaceable>file</replaceable> as the configuration
            file for &dhpackage;.  By default, a file named
            <filename>&dhpackage;.conf</filename> is used if it exists.
            If the name of the configuration file is relative, it is
            interpreted as relative to the <filename
            class="directory">CVSROOT</filename> administrative
            directory of the repository.  <option>--config</option> is
            incompatible with <option>--no-config</option>.
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--no-config</option></term>
        <listitem>
          <para>
            Do not use a configuration file for &dhpackage;.  This can
            be used to disable the use of the default configuration
            file.  <option>--no-config</option> is incompatible with
            <option>--config</option>.  Note that it's not normally
            useful to specify this option, but it may be useful when
            you want to allow changes to any branch within a single
            CVS module, but use a more sophisticated configuration for
            the rest of the repository.
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--cvsroot <replaceable>path</replaceable></option></term>
        <listitem>
          <para>
            Use <replaceable>path</replaceable> as the value for the
            <envar>CVSROOT</envar> environment variable.  This is
            usually not needed.
          </para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><option>--help</option></term>
        <term><option>-h</option></term>
        <listitem>
          <para>
            Print a summary of the command line options to standard
            output.
          </para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1>
    <title>Bugs</title>
    <para>
      There are probably some bugs.  If you find them, please
      report them to the maintainers using the <ulink
      url="http://sourceforge.net/projects/cvs-syncmail/">bug
      tracker</ulink>.
    </para>
  </refsect1>

  <refsect1>
    <title>See Also</title>
    <para>
      The <ulink url="http://sourceforge.net/projects/cvs-syncmail/"
      >&dhpackage; page</ulink> on &sourceforge;.
    </para>

    <para>
      The <ulink url="http://www.cvshome.org/">CVS home page</ulink>.
    </para>
  </refsect1>

  <refsect1>
    <title>Author</title>
    <para>
      &dhpackage; was originally written by Fred Drake.
    </para>
    <para>
      This manual page was written by &dhusername; &dhemail;.
    </para>
  </refsect1>
</refentry>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->

[Cvs-syncmail] syncmail sample.conf,NONE,1.1.2.1 syncmail.conf,1.1.2.2,NONE

From: Fred L. D. <fd...@us...> - 2003-07-15 17:43:00

Update of /cvsroot/cvs-syncmail/syncmail
In directory sc8-pr-cvs1:/tmp/cvs-serv5197

Added Files:
      Tag: new-config-branch
	sample.conf 
Removed Files:
      Tag: new-config-branch
	syncmail.conf 
Log Message:
Rename syncmail.conf to sample.conf since it is only intended as a sample,
not as a template.


--- NEW FILE: sample.conf ---
; In values, substitutions for $BRANCH, $CVSROOT, and $HOSTNAME are
; available.  These may also be spelled with curlies (for example:
; ${BRANCH}).  These are replaced by the branch name (or the empty
; string for the trunk), the CVSROOT environment variable (not the
; root specified using --cvsroot), and the hostname (from the HOSTNAME
; environment variable or, if not set, the fully-qualified hostname).

[general]
; miscellaneous
verbose        = true
email          = true

; the kind of diff we generate
context-lines  = 2
diff-type      = unified

; how email is generated
from-host      = $HOSTNAME
reply-to       =
smtp-server    = localhost
subject-prefix =
to             = cvs...@li...

[branch]
; the * branch applies to all branches
subject-prefix = $BRANCH:

[branch my-project-branch]
email          = false

[branch another-branch]
subject-prefix = [Special]
to             = my...@ex...

--- syncmail.conf DELETED ---

[Cvs-syncmail] syncmail/doc syncmail.sgml,1.3,1.4 syncmail.1,1.3,1.4

From: Fred L. D. <fd...@us...> - 2003-07-15 16:13:53

Update of /cvsroot/cvs-syncmail/syncmail/doc
In directory sc8-pr-cvs1:/tmp/cvs-serv20085

Modified Files:
	syncmail.sgml syncmail.1 
Log Message:
Use normal case for section headings; stylesheets can transform if desired.

Index: syncmail.sgml
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/doc/syncmail.sgml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- syncmail.sgml	8 Jul 2003 21:20:23 -0000	1.3
+++ syncmail.sgml	15 Jul 2003 16:13:50 -0000	1.4
@@ -13,13 +13,13 @@
   <!ENTITY dhfirstname "<firstname>Fred</firstname>">
   <!ENTITY dhsurname   "<surname>Drake</surname>">
   <!-- Please adjust the date whenever revising the manpage. -->
-  <!ENTITY dhdate      "<date>July 8, 2003</date>">
+  <!ENTITY dhdate      "<date>July 15, 2003</date>">
   <!-- SECTION should be 1-8, maybe w/ subsection other parameters are
        allowed: see man(7), man(1). -->
   <!ENTITY dhsection   "<manvolnum>1</manvolnum>">
   <!ENTITY dhemail     "<email>fd...@ac...</email>">
   <!ENTITY dhusername  "Fred L. Drake, Jr.">
-  <!ENTITY dhucpackage "<refentrytitle>SYNCMAIL</refentrytitle>">
+  <!ENTITY dhucpackage "<refentrytitle>syncmail</refentrytitle>">
   <!ENTITY dhpackage   "syncmail">
 
   <!ENTITY debian      "<productname>Debian GNU/Linux</productname>">
@@ -73,7 +73,7 @@
   </refsynopsisdiv>
 
   <refsect1>
-    <title>DESCRIPTION</title>
+    <title>Description</title>
     <para>
       <command>&dhpackage;</command> sends out notifications of CVS
       commits via email, including the patch that was applied for
@@ -109,7 +109,7 @@
   </refsect1>
 
   <refsect1>
-    <title>SETTING UP SYNCMAIL</title>
+    <title>Setting Up syncmail</title>
     <para>
       Setting up &dhpackage; is not difficult, but there are usually
       several steps:
@@ -266,7 +266,7 @@
   </refsect1>
 
   <refsect1>
-    <title>OPTIONS</title>
+    <title>Options</title>
     <para>
       When an option includes an argument, you may specify the
       argument either separate ("-d output") or mashed ("-doutput").
@@ -403,7 +403,7 @@
   </refsect1>
 
   <refsect1>
-    <title>BUGS</title>
+    <title>Bugs</title>
     <para>
       There are probably some bugs.  If you find them, please
       report them to the maintainers using the <ulink
@@ -413,7 +413,7 @@
   </refsect1>
 
   <refsect1>
-    <title>ALTERNATIVES</title>
+    <title>Alternatives</title>
     <para>
       Other people have written tools that serve similar purposes, but
       not all of these are meant to support CVS repositories accessed
@@ -440,7 +440,7 @@
   </refsect1>
 
   <refsect1>
-    <title>SEE ALSO</title>
+    <title>See Also</title>
     <para>
       The <ulink url="http://sourceforge.net/projects/cvs-syncmail/"
       >&dhpackage; page</ulink> on &sourceforge;.
@@ -452,7 +452,7 @@
   </refsect1>
 
   <refsect1>
-    <title>AUTHOR</title>
+    <title>Author</title>
     <para>
       &dhpackage; was originally written by Barry Warsaw to send mail
       based on checkins to the Python project.  Barry continues to

Index: syncmail.1
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/doc/syncmail.1,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- syncmail.1	8 Jul 2003 21:20:23 -0000	1.3
+++ syncmail.1	15 Jul 2003 16:13:50 -0000	1.4
@@ -3,7 +3,7 @@
 .\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
 .\" Please send any bug reports, improvements, comments, patches, 
 .\" etc. to Steve Cheng <st...@gg...>.
-.TH "SYNCMAIL" "1" "08 July 2003" "" ""
+.TH "SYNCMAIL" "1" "15 July 2003" "" ""
 
 .SH NAME
 syncmail \- Send email notifications of CVS activity

[Cvs-syncmail] syncmail/doc syncmail.sgml,1.3.2.1,1.3.2.2

From: Fred L. D. <fd...@us...> - 2003-07-14 18:23:23

Update of /cvsroot/cvs-syncmail/syncmail/doc
In directory sc8-pr-cvs1:/tmp/cvs-serv360

Modified Files:
      Tag: new-config-branch
	syncmail.sgml 
Log Message:
Remove the "required" indicators from positional command-line
arguments; nothing is absolutely required if the config file provides
enough information.


Index: syncmail.sgml
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/doc/syncmail.sgml,v
retrieving revision 1.3.2.1
retrieving revision 1.3.2.2
diff -u -d -r1.3.2.1 -r1.3.2.2
--- syncmail.sgml	10 Jul 2003 14:08:24 -0000	1.3.2.1
+++ syncmail.sgml	14 Jul 2003 18:23:17 -0000	1.3.2.2
@@ -69,8 +69,8 @@
       <arg>--subject-prefix <replaceable>string</replaceable></arg>
       <arg>-S <replaceable>string</replaceable></arg>
       <arg><option>--help</option> | <option>-h</option></arg>
-      <arg choice="req">%{sSv}</arg>
-      <arg choice="req" rep="repeat">email</arg>
+      <arg>%{sSv}</arg>
+      <arg rep="repeat">email</arg>
     </cmdsynopsis>
   </refsynopsisdiv>

[Cvs-syncmail] syncmail syncmail,1.36.2.17,1.36.2.18

From: Fred L. D. <fd...@us...> - 2003-07-14 18:12:53

Update of /cvsroot/cvs-syncmail/syncmail
In directory sc8-pr-cvs1:/tmp/cvs-serv28157

Modified Files:
      Tag: new-config-branch
	syncmail 
Log Message:
- update commented-out code


Index: syncmail
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/syncmail,v
retrieving revision 1.36.2.17
retrieving revision 1.36.2.18
diff -u -d -r1.36.2.17 -r1.36.2.18
--- syncmail	14 Jul 2003 17:01:32 -0000	1.36.2.17
+++ syncmail	14 Jul 2003 18:12:50 -0000	1.36.2.18
@@ -371,7 +371,7 @@
 ##            name = string.split(line, "/")[1]
 ##            dirname = namekey(prefix, name)
 ##            if os.path.isdir(dirname):
-##                m = load_change_info(dirname)
+##                m = load_entries(dirname)
 ##                mapping.update(m)
         if line[0] == "/":
             # normal file

1117 messages has been excluded from this view by a project administrator.

Flat | Threaded

<< < 1 .. 15 16 17 18 19 .. 26 > >> (Page 17 of 26)

cvs-syncmail-talk Mailing List for syncmail (Page 17)

cvs-syncmail-talk — User &amp; developer discussions for the &quot;syncmail&quot; CVS checkin notification tool

cvs-syncmail-talk — User & developer discussions for the "syncmail" CVS checkin notification tool