Yeah, that often stops me. I correct obvious typos when I see them, and 
add stuff when I know it's correct, but I'm hesitant to change other 
folk's stuff. But if you see something you *know* is out of date, go 
ahead and change it.

Actually, I haven't been to the wiki in months...

Chas.

James Matlik wrote:
> That thought did come to me, but you are correct.  I can see 
> inconsistencies but don't know enough to be certain I wouldn't lead 
> others astray.  It is also possible work in progress that I am seeing 
> mid-stream.
> 
> On Mon, Mar 9, 2009 at 6:43 AM, Charles F. Munat <[email protected] 
> <mailto:[email protected]>> wrote:
> 
> 
>     You can actually update the wiki yourself, I think. It's probably faster
>     that writing about it to the list, unless you're not sure you're
>     correct...
> 
>     Chas.
> 
>     James Matlik wrote:
>      >
>      > I have found another inconsistency on the wiki at
>      > http://wiki.liftweb.net/index.php?title=HowTo_run_examples.  The wiki
>      > has several links for obtaining the version 1.0 example source code;
>      > however, only the links for downloading the WAR files work.  All the
>      > other links for obtaining the sources are dead.  The google code
>     project
>      > doesn't even have a lift-1.0 tag in the subversion repository;
>     lift-0.8
>      > appears to be the most recent.  How should code be pulled from svn?
>      > Should we use the lift-0.8 tag or pull from head?  Or has the
>     code moved
>      > to git, so the svn repository should be considered legacy?
>      >
>      > Thanks,
>      > James
>      >
>      > >
> 
> 
> 
> 
> > 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to