Antonio,
Absolutely. But all that was what I was considering under "internal" useĀfor
the project developers/committers. They can use whatever they want. I was
only addressing the possible utility of *exposing* the SVN repository under
these circumstances. And whether it might be more or less work for Lukas...
It just seemed like occasionally publishing SynaSnaps might still be easier
and less work for him. [And if he uses the public repository as you suggest
(and I like!) that means that you and I will occasionally update our copies
with broken code that won't even compile, since Lukas stopped working on the
wifi connection at the cafe and won't get back to the code till after some
good family time, like at least <G> a week at the mountain resort spa!]
Otherwise, an exposed repository seems pretty good for those of us "on the
outside" wanting to look at and test the latest code...
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public
