[Systers-dev] missing source code files

[Jennifer Redman]

Yes you need to pull the production branch.  The wishlist branch was  
merged and rolled into production so really its only use at this point  
is to see what Anna worked in last summer. If you use that branch you  
won't have the latest code.

Everyone should start with prod or stable.

I'll take a look at the wiki. Sorry for the confusion and nice catch.

Jen



On Apr 3, 2010, at 11:28, "Anne Gunn" <ompeag at wyoming.com> wrote:

>   I've checked out both the wishlist branch and the development branch
>   from bazaar, per the instructions on the wiki.
>   I started trying to fix the first of the trial bugs (missing +new on
>   the text at the top of a digest email) and was having just a heck  
> of a
>   time finding the code to work on.  Finally, I swallowed my pride and
>   peeked at beachBrake's patch for this.
>   It's in a file that I don't have in either of the branches I checked
>   out:
>   Mailman/Handlers/ToDigest.py
>   The only files I have in my Mailman/Handlers folder are:
>   CookieHeaders.py
>   Decorate.py
>   Dlists.py
>   Moderate.py
>   The wiki instructions say specifically I can start with a checkout  
> from
>   wishlist.  But, in fact, do I have to seed the fileset with a  
> checkout
>   from the production/stable branch first?
>   ag
>   -----------------------
>   Anne Gunn
>   ompeag @ wyoming.com
>   307 673 5234
>
>
> To unsubscribe from this conversation, send email to <systers-dev+bazaar+unsubscribe at systers.org 
> > or visit <http://systers.org/mailman/options/systers-dev?override=91&preference=0 
> >
> To contribute to this conversation, use your mailer's reply-all or  
> reply-group command or send your message to systers-dev+bazaar at systers.org
> To start a new conversation, send email to <systers-dev+new at systers.org 
> >
> To unsubscribe entirely from systers-dev, send email to <systers-dev-request at systers.org 
> > with subject unsubscribe.