[Mailman-Developers] Patching 2.0.13 for eVote

[Marilyn Davis]

Thank you.

I see.  I was afraid of that.  I don't have write-access to cvs at
sourceforge, so I can't do that.

I don't think I should add stuff at sourceforge because we want people
to evaluate eVote before we put it into the repository.

So, I'll put the new files in eVote's distribution and the
installation will copy them into the mailman tree.  It doesn't really
matter since the mailman/eVote patch isn't any good without eVote.
It'll be invisible to the installer anyway.

Thank you again.

Marilyn

On Fri, 27 Dec 2002, Simone Piunno wrote:

> On Thu, Dec 26, 2002 at 10:30:46AM -0800, Marilyn Davis wrote:
> 
> > I'm messing up somehow.  I give this command:
> > 
> > [root at Xoko mailman]# cvs diff -N -u > /tmp/eVote-patch.txt
> > 
> > But my patch starts like:
> > 
> > ? bin/eVote_queries.py
> > ? templates/eVote.txt
> > ? templates/eVotePetition.txt
> > 
> > and those files aren't in there.
> 
> "cvs diff" only looks in checked-out + cvs-added files.
> If you create brand new files (instead of changing existing ones)
> cvs diff will ignore them.... unless you "cvs add newfile" before
> diffing.
> 
> Therefore, you should:
> 
> 1. cvs add any new file
> 2. cvs diff -N -u
> 
> info:/cvs for details.
> -- 
> Adde parvum parvo magnus acervus erit.
> Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo
>