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

[Cvs-syncmail] syncmail alternative

[Joost v. B. <j.e...@uv...>]

Hi,

In the syncmail manpages, you ask to get informed about tools that serve
similar purposes.  I've been using log_accum before, a Perl script.  You
can get it from

http://savannah.gnu.org/cgi-bin/viewcvs/savannah/savannah/cvsadmin/log_accum

(And lots of other places too, the tool seems to be severely forked.)

You might want to add this to your documentation.

Thanks for maintaining syncmail!  Bye,

Joost

--=20
Joost van Baal                                http://banach.uvt.nl/
                                                 Tilburg University
j.e...@uv...                                  The Netherlands

[Cvs-syncmail] Branches

[Harald P. de L. <hp...@os...>]

Hi List..

Is it possible to use different email addresses for different branches 
in a module, similar to how using different email addresses is possible 
with different modules?

Thanks for your time,

-- 
Harald Ponce de Leon
osCommerce, Open Source E-Commerce Solutions
http://www.oscommerce.com

Re: [Cvs-syncmail] Using syncmail to do some automatic log file creationg.

[Klaus J. R. <Kla...@at...>]

Srinath Avadhanula wrote:

> I have been looking at the syncmail source and much to my surprise, I

> couldn't figure out where it was reading in the log message. In
> blast_mail, the diff itself is calculated, but where is the log message
> itself being read in?
>
> With a little help, I am sure I will be able to get this done.

The log message is read from STDIN

--
Klaus Johannes Rusch
Kla...@at...
http://www.atmedia.net/KlausRusch/

[Cvs-syncmail] Using syncmail to do some automatic log file creationg.

[Srinath A. <sr...@fa...>]

Hello,

I have been using the excellent syncmail utility for many moons now :)
Thanks!

Recently, I have thought that it might be a cool idea to have a log file
be updated automatically on every commit, but a little intelligently. If
the log message contains something like:

--------%<--------
<log>
Changelog message
</log>
Some other stuff
--------%<--------

Then only the part between <log> and </log> should go into the Changelog
file... The same thing for <bug></bug> etc.

I have been looking at the syncmail source and much to my surprise, I
couldn't figure out where it was reading in the log message. In
blast_mail, the diff itself is calculated, but where is the log message
itself being read in?

With a little help, I am sure I will be able to get this done.

Many thanks,

Srinath

PS: I am not subscribed to the list, so a CC to me will be highly
appreciated.

[Cvs-syncmail] syncmail syncmail,1.25,1.26

[Greg W. <gw...@us...>]

Update of /cvsroot/cvs-syncmail/syncmail
In directory usw-pr-cvs1:/tmp/cvs-serv26909

Modified Files:
	syncmail 
Log Message:
Docstring typo fix.
Whitespace fixes.


Index: syncmail
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/syncmail,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- syncmail	14 Nov 2002 16:15:44 -0000	1.25
+++ syncmail	15 Nov 2002 20:51:36 -0000	1.26
@@ -38,8 +38,8 @@
 Where options are:
 
     --cvsroot=<path>
-    	Use <path> as the environment variable CVSROOT.  Otherwise this
-    	variable must exist in the environment.
+        Use <path> as the environment variable CVSROOT.  Otherwise this
+        variable must exist in the environment.
 
     --context=#
     -C #
@@ -65,7 +65,7 @@
     --fromhost=hostname
     -f hostname
         The hostname that email messages appear to be coming from.  The From:
-        header will of the outgoing message will look like user@hostname.  By
+        header of the outgoing message will look like user@hostname.  By
         default, hostname is the machine's fully qualified domain name.
 
     --help / -h
@@ -111,7 +111,7 @@
         else:
             fqdn = 'localhost.localdomain'
         return fqdn
-    
+
 
 from cStringIO import StringIO
 

[Cvs-syncmail] syncmail syncmail,1.24,1.25

[Fred L. D. <fd...@us...>]

Update of /cvsroot/cvs-syncmail/syncmail
In directory usw-pr-cvs1:/tmp/cvs-serv25859

Modified Files:
	syncmail 
Log Message:
Add a couple of comments, since I don't look at this very often.  ;-)


Index: syncmail
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/syncmail,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- syncmail	11 Nov 2002 17:42:07 -0000	1.24
+++ syncmail	14 Nov 2002 16:15:44 -0000	1.25
@@ -176,6 +176,7 @@
         # quote it with single-quotes.
         filestr = "'" + file + "'"
     if oldrev == 'NONE':
+        # File is being added.
         try:
             if os.path.exists(file):
                 fp = open(file)
@@ -200,6 +201,7 @@
     elif newrev == 'NONE':
         lines = ['--- %s DELETED ---\n' % file]
     else:
+        # File has been changed.
         # This /has/ to happen in the background, otherwise we'll run into CVS
         # lock contention.  What a crock.
         if contextlines > 0:

[Cvs-syncmail] Avoiding CVS lock in syncmail

[Fred L. D. Jr. <fd...@ac...>]

After hacking up a commitinfo script yesterday, it occurred to me that
syncmail should be able to use "rcsdiff" instead of "cvs diff" to
generate diffs, and not run afoul of the CVS lock.  Perhaps the
backgrounding of syncmail could be avoided.

If anyone has time on their hands ;-) it might make a nice project to
see what can be done.


  -Fred

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

[Cvs-syncmail] Re: Bug#168832: cvs-syncmail: doesn't work.

[Neil S. <ns...@cs...>]

On Tue, Nov 12, 2002 at 04:34:47PM -0700, Kevin Rosenberg wrote:
> Hello cvs-syncmail guys,

> The Debian cvs-syncmail package has already gotten a new user. Neil
> Spring had confusion reading the output of --help and he put %s as the
> argument to syncmail. He proposes adding some more information to that
> output, perhaps along the lines of what he wrote below to help
> others who
> might be led astry.

I actually would prefer the five-character change to modify
the example at the top of the output from:
    mymodule /path/to/this/script %s som...@yo...
to:
    mymodule /path/to/this/script %{sVv} som...@yo...

The rest was a tongue-in-cheek comment after being told to
RTFM.

thanks,
-neil

[Cvs-syncmail] Re: Bug#168832: cvs-syncmail: doesn't work.

[Kevin R. <ke...@ro...>]

Hello cvs-syncmail guys,

The Debian cvs-syncmail package has already gotten a new user. Neil
Spring had confusion reading the output of --help and he put %s as the
argument to syncmail. He proposes adding some more information to that
output, perhaps along the lines of what he wrote below to help others who
might be led astry.
 
Best,

-- 
       Kevin Rosenberg        |  .''`.  ** Debian GNU/Linux **
  http://b9.com/debian.html   | : :' :      The  universal
  GPG signed and encrypted    | `. `'      Operating System
     messages accepted.       |   `-    http://www.debian.org/


Neil Spring wrote:
>  If the %s in the loginfo file is not %{sVv}, syncmail
>  will fail miserably with error messages you won't 
>  understand, making the example at the top of this file 
>  confusing and useless.  So be sure to ignore the example
>  at the top of this message and instead use: 
>  mymodule /usr/bin/syncmail %{sVv} som...@yo....
> 
> > Which would have been more clear.  
> 
> All I'm asking is that the example at the top (well outside
> the "usage" statement) be made usable.

[Cvs-syncmail] syncmail syncmail,1.23,1.24

[Greg W. <gw...@us...>]

Update of /cvsroot/cvs-syncmail/syncmail
In directory usw-pr-cvs1:/tmp/cvs-serv3279

Modified Files:
	syncmail 
Log Message:
Add quotename() and rfc822_specials_re so we only quote real names
in the "From" header when we really need to.  Fixes SF bug #592836.


Index: syncmail
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/syncmail,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- syncmail	8 Nov 2002 22:01:36 -0000	1.23
+++ syncmail	11 Nov 2002 17:42:07 -0000	1.24
@@ -223,6 +223,16 @@
 
 
 
+rfc822_specials_re = re.compile(r'[\(\)\<\>\@\,\;\:\\\"\.\[\]]')
+
+def quotename(name):
+    if name and rfc822_specials_re.search(name):
+        return '"%s"' % name.replace('"', '\\"')
+    else:
+        return name
+
+
+
 def blast_mail(subject, people, filestodiff, contextlines, fromhost, replyto):
     # cannot wait for child process or that will cause parent to retain cvs
     # lock for too long.  Urg!
@@ -241,13 +251,13 @@
         sys.stdout = s
         try:
             vars = {'address' : address,
-                    'name'    : name,
+                    'name'    : quotename(name),
                     'people'  : string.join(people, COMMASPACE),
                     'subject' : subject,
                     'version' : __version__,
                     }
             print '''\
-From: "%(name)s" <%(address)s>
+From: %(name)s <%(address)s>
 To: %(people)s''' % vars
             if replyto:
                 print 'Reply-To: %s' % replyto

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[Greg W. <gw...@py...>]

On 08 November 2002, Barry A. Warsaw said:
>     KR> The PSF License looks fine. On the other hand, it is very
>     KR> similar to a BSD license except that the copyright is owned by
>     KR> the PSF. Rather that going through the efforts of assigning
>     KR> copyrights, perhaps sometime like the below would be
>     KR> acceptable.
> 
> I'd be happy with that.  It's in the spirit of the original Python
> license.  Fred, Greg, and Zooko, what do you guys think?

Whatever.  As long as it's open source I don't much care.

        Greg
-- 
Greg Ward <gw...@py...>                         http://www.gerg.ca/
I have the power to HALT PRODUCTION on all TEENAGE SEX COMEDIES!!

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[Kevin R. <ke...@ro...>]

Barry A. Warsaw wrote:
> I'm going to make a leap of faith and assume Greg's on board with the
> BSD-ish license. ;) I just checked in a LICENSE file and added
> copyright notices to the file.  I hope that'll be enough for Kevin to
> add it to Debian.

Great -- I'm very happy to be able to redistribute this very helpful
product.

> I stil want to leave open the possibility of PSF donation, if the PSF
> ever starts accepting such things. ;)

Since you own the copyright, you can always change the licensing on
any time. Of course, copies of your software distributed with the
current license stay with the current license. But, that doesn't
affect your ability to relicense or to assign your copyright.

Thanks very much for your gift.

-- 
       Kevin Rosenberg        |  .''`.  ** Debian GNU/Linux **
  http://b9.com/debian.html   | : :' :      The  universal
  GPG signed and encrypted    | `. `'      Operating System
     messages accepted.       |   `-    http://www.debian.org/

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[<ba...@py...>]

I'm going to make a leap of faith and assume Greg's on board with the
BSD-ish license. ;) I just checked in a LICENSE file and added
copyright notices to the file.  I hope that'll be enough for Kevin to
add it to Debian.

I stil want to leave open the possibility of PSF donation, if the PSF
ever starts accepting such things. ;)

-Barry

[Cvs-syncmail] syncmail README,1.1,1.2

[Barry W. <bw...@us...>]

Update of /cvsroot/cvs-syncmail/syncmail
In directory usw-pr-cvs1:/tmp/cvs-serv5668

Modified Files:
	README 
Log Message:
Add a copyright notice and a pointer to the LICENSE file.  I really
don't want to include the whole LICENSE file as a comment in this
file.


Index: README
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/README,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- README	3 May 2002 21:30:23 -0000	1.1
+++ README	8 Nov 2002 22:02:25 -0000	1.2
@@ -13,5 +13,7 @@
 
     cvs...@li...
 
+See the LICENSE file for copyright information.
+
 Our thanks to Zooko for helping improve the security of the script.
 -Barry Warsaw & Fred Drake (maintainers)

[Cvs-syncmail] syncmail syncmail,1.22,1.23

[Barry W. <bw...@us...>]

Update of /cvsroot/cvs-syncmail/syncmail
In directory usw-pr-cvs1:/tmp/cvs-serv5419

Modified Files:
	syncmail 
Log Message:
Add a copyright notice and a pointer to the LICENSE file.  I really
don't want to include the whole LICENSE file as a comment in this
file.


Index: syncmail
===================================================================
RCS file: /cvsroot/cvs-syncmail/syncmail/syncmail,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- syncmail	7 Nov 2002 15:02:10 -0000	1.22
+++ syncmail	8 Nov 2002 22:01:36 -0000	1.23
@@ -1,5 +1,9 @@
 #! /usr/bin/python
 
+# Copyright (c) 2002, Barry Warsaw, Fred Drake, and contributors
+# All rights reserved.
+# See the accompanying LICENSE file for details.
+
 # NOTE: Until SourceForge installs a modern version of Python on the cvs
 # servers, this script MUST be compatible with Python 1.5.2.
 

[Cvs-syncmail] syncmail LICENSE,NONE,1.1

[Barry W. <bw...@us...>]

Update of /cvsroot/cvs-syncmail/syncmail
In directory usw-pr-cvs1:/tmp/cvs-serv4495

Added Files:
	LICENSE 
Log Message:
A BSD-ish license.


--- NEW FILE: LICENSE ---
Copyright (c) 2002, Barry Warsaw, Fred Drake, and contributors
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above
      copyright notice, this list of conditions and the following
      disclaimer in the documentation and/or other materials provided
      with the distribution.
    * Neither the names of the authors nor the names of its
      contributors may be used to endorse or promote products derived
      from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[Fred L. D. Jr. <fd...@ac...>]

Barry A. Warsaw writes:
 > I'd be happy with that.  It's in the spirit of the original Python
 > license.  Fred, Greg, and Zooko, what do you guys think?

I'm fine with a BSDish license.


  -Fred

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

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[Zooko <zo...@zo...>]

> I'd be happy with that.  It's in the spirit of the original Python
> license.  Fred, Greg, and Zooko, what do you guys think?

+1 on BSD-ish license

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[<ba...@zo...>]

>>>>> "KR" == Kevin Rosenberg <ke...@ro...> writes:

    >> We certainly could donate syncmail to the PSF, but there (still
    >> :( ) isn't a really great mechanism for doing.  The best that's
    >> out there is a proposed contribution form:
    >> http://www.python.org/psf/psf-contributor-agreement.html

    KR> I'm not familiar with other software that has had copyrights
    KR> assigned to the PSF, but I suspect that it has happed.

You might be wrong about that. ;)

    KR> The PSF License looks fine. On the other hand, it is very
    KR> similar to a BSD license except that the copyright is owned by
    KR> the PSF. Rather that going through the efforts of assigning
    KR> copyrights, perhaps sometime like the below would be
    KR> acceptable.

I'd be happy with that.  It's in the spirit of the original Python
license.  Fred, Greg, and Zooko, what do you guys think?

    KR> Thanks again for discussing this. I hope that a license is
    KR> chosen soon so that I can add your fine product to the Debian
    KR> distribution.

-Barry

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[Kevin R. <ke...@ro...>]

Barry A. Warsaw wrote:
> I'm nearly positive I chose "Python license" when I set up the
> project.  Certainly the intent was to put a Pythonic license on the
> thing, and perhaps eventually donate it to the PSF.

Hi Barry, thanks for the reply.

> Unfortunately, if you actually read the PSF license for Python, it's
> pretty specific to Python and the fact that the PSF is the entity that
> is actually doing the licensing.  It doesn't really apply out of the
> box to syncmail.

Yeah, I saw that.

> We certainly could donate syncmail to the PSF, but there (still :(
> ) isn't a really great mechanism for doing.  The best that's out there
> is a proposed contribution form:
> 
>     http://www.python.org/psf/psf-contributor-agreement.html

I'm not familiar with other software that has had copyrights assigned
to the PSF, but I suspect that it has happed.

> BTW, I brought this up on the PSF mailing lists back in May, specific
> for syncmail.  Like too many other things, we lost interest and the
> thread died without traction (I blame myself for that).  At the time,
> I proposed the following license.  Note that that it would require
> donating the software to the PSF, and then there's the question of who
> would need to do the donating (everyone who's committed changes to the
> code, just me, etc...)

The PSF License looks fine. On the other hand, it is very similar to a
BSD license except that the copyright is owned by the PSF. Rather that
going through the efforts of assigning copyrights, perhaps sometime
like the below would be acceptable.

Thanks again for discussing this. I hope that a license is chosen soon
so that I can add your fine product to the Debian distribution.

-- 
       Kevin Rosenberg        |  .''`.  ** Debian GNU/Linux **
  http://b9.com/debian.html   | : :' :      The  universal
  GPG signed and encrypted    | `. `'      Operating System
     messages accepted.       |   `-    http://www.debian.org/


Copyright (C) Barry Warsaw, Fred Drake, and contributors.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products
   derived from this software without specific prior written
   permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[<ba...@zo...>]

>>>>> "Fred" == Fred L Drake, Jr <fd...@ac...> writes:

    >> I started usign cvs-syncmail and I like it a lot. I'd like to
    >> package this for the Debian GNU/Linux distribution. I see a
    >> copyright in docs/syncmail.sgml, but there is no license that
    >> specifies rights of use or redistribution for
    >> cvs-syncmail. Without such a license, I can't distribute
    >> cvs-syncmail as a Debian package.

    Fred> I don't think we've ever really talked much about the
    Fred> license for syncmail, and I'm not sure where to find what
    Fred> license information was provided to SourceForge.  Barry, do
    Fred> you remember how you set it up?

I'm nearly positive I chose "Python license" when I set up the
project.  Certainly the intent was to put a Pythonic license on the
thing, and perhaps eventually donate it to the PSF.

    Fred> If no one can remember what the license is, I'll propose we
    Fred> stick the PSF license on it.  ;-)

Unfortunately, if you actually read the PSF license for Python, it's
pretty specific to Python and the fact that the PSF is the entity that
is actually doing the licensing.  It doesn't really apply out of the
box to syncmail.

We certainly could donate syncmail to the PSF, but there (still :(
) isn't a really great mechanism for doing.  The best that's out there
is a proposed contribution form:

    http://www.python.org/psf/psf-contributor-agreement.html

BTW, I brought this up on the PSF mailing lists back in May, specific
for syncmail.  Like too many other things, we lost interest and the
thread died without traction (I blame myself for that).  At the time,
I proposed the following license.  Note that that it would require
donating the software to the PSF, and then there's the question of who
would need to do the donating (everyone who's committed changes to the
code, just me, etc...)

-Barry

-------------------- snip snip --------------------
PSF LICENSE AGREEMENT 1.0
-------------------------

1. This LICENSE AGREEMENT is between the Python Software Foundation
("PSF"), and the Individual or Organization ("Licensee") accessing and
otherwise using PSF software ("the Software") in source or binary form
and its associated documentation.

2. Subject to the terms and conditions of this License Agreement, PSF
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use the Software
alone or in any derivative version, provided, however, that PSF's
License Agreement and PSF's notice of copyright are retained in the
Software alone or in any derivative version prepared by Licensee.

3. In the event Licensee prepares a derivative work that is based on
or incorporates the Software or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to the Software.

4. PSF is making the Software available to Licensee on an "AS IS"
basis.  PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.

5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING THE
SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE
POSSIBILITY THEREOF.

6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.

7. Nothing in this License Agreement shall be deemed to create any
relationship of agency, partnership, or joint venture between PSF and
Licensee.  This License Agreement does not grant permission to use PSF
trademarks or trade name in a trademark sense to endorse or promote
products or services of Licensee, or any third party.

8. By copying, installing or otherwise using the Software, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.

Re: [Cvs-syncmail] What is cvs-syncmail's license?

[Fred L. D. Jr. <fd...@ac...>]

Kevin Rosenberg writes:
 > I started usign cvs-syncmail and I like it a lot. I'd like to package
 > this for the Debian GNU/Linux distribution. I see a copyright in
 > docs/syncmail.sgml, but there is no license that specifies rights of
 > use or redistribution for cvs-syncmail. Without such a license, I
 > can't distribute cvs-syncmail as a Debian package.

I don't think we've ever really talked much about the license for
syncmail, and I'm not sure where to find what license information was
provided to SourceForge.  Barry, do you remember how you set it up?

If no one can remember what the license is, I'll propose we stick the
PSF license on it.  ;-)


  -Fred

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

[Cvs-syncmail] What is cvs-syncmail's license?

[Kevin R. <ke...@ro...>]

Hello CVS-Syncmail list,

I started usign cvs-syncmail and I like it a lot. I'd like to package
this for the Debian GNU/Linux distribution. I see a copyright in
docs/syncmail.sgml, but there is no license that specifies rights of
use or redistribution for cvs-syncmail. Without such a license, I
can't distribute cvs-syncmail as a Debian package.

What is the license for cvs-syncmail?

Thanks for your time and the excellent tool.

--
       Kevin Rosenberg        |  .''`.  ** Debian GNU/Linux **
  http://b9.com/debian.html   | : :' :      The  universal
  GPG signed and encrypted    | `. `'      Operating System
     messages accepted.       |   `-    http://www.debian.org/

Re: [Cvs-syncmail] Patch: fix bug #592836

[Greg W. <gw...@py...>]

On 29 October 2002, I said:
> While I'm in the mood, here's another patch for syncmail.  This one
> fixes bug #592836

Here's a revised version of that patch, relative to current CVS:

--- syncmail	7 Nov 2002 15:02:10 -0000	1.22
+++ syncmail	7 Nov 2002 15:04:36 -0000
@@ -219,6 +219,16 @@
 
 
 
+rfc822_specials_re = re.compile(r'[\(\)\<\>\@\,\;\:\\\"\.\[\]]')
+
+def quotename(name):
+    if name and rfc822_specials_re.search(name):
+        return '"%s"' % name.replace('"', '\\"')
+    else:
+        return name
+
+
+
 def blast_mail(subject, people, filestodiff, contextlines, fromhost, replyto):
     # cannot wait for child process or that will cause parent to retain cvs
     # lock for too long.  Urg!
@@ -237,13 +247,13 @@
         sys.stdout = s
         try:
             vars = {'address' : address,
-                    'name'    : name,
+                    'name'    : quotename(name),
                     'people'  : string.join(people, COMMASPACE),
                     'subject' : subject,
                     'version' : __version__,
                     }
             print '''\
-From: "%(name)s" <%(address)s>
+From: %(name)s <%(address)s>
 To: %(people)s''' % vars
             if replyto:
                 print 'Reply-To: %s' % replyto


Barry already said +1 for this, so I'm going to test it out in real life
and then check this change in.

        Greg
-- 
Greg Ward <gw...@py...>                         http://www.gerg.ca/
I don't believe there really IS a GAS SHORTAGE.. I think it's all just
a BIG HOAX on the part of the plastic sign salesmen -- to sell more numbers!!

Re: [Cvs-syncmail] Patch: add Reply-To header

[Greg W. <gw...@py...>]

On 07 November 2002, Barry A. Warsaw said:
>     GW> OK, I finally got around to actually testing my second attempt
>     GW> at the "add Reply-To" patch.  It worked.
> 
>     GW> Barry, can I check this in now?
> 
> +1

OK, my "reply-to" patch is checked in.

        Greg