On Sun, Jul 26, 2009 at 4:43 PM, Philip Brown <[email protected]> wrote: > On Sun, Jul 26, 2009 at 11:34:57AM +0200, Trygve Laugstøl wrote: >> Can you explain what the security reason for not putting it an SCM is? > > "a" source code control mechanism, I dont have much problem with. > putting it in a PUBLIC one, is where my concerns lay. > > Beyond that, I dont see the need to force everyone to use one particular > type of scm, just for small web page "code". > If the assorted people working on opencsw web stuff agree to standardize on > one internal-only scheme, i'd go along with it. But frankly, most of the > web related stuff is small enough that the old cycle of > > "make a save copy, tweak with the new stuff, publish it, forget about old > stuff" > > is perfectly adequate.
Okay, so what's the process? I can't write to the htdocs directory, so what do I do? Make my own copy of everything and create a patch? When I have a patch ready, say, http://www.opencsw.org/~maciej/0001-Parseable-HTML-in-mirrors.shtml.patch -- what do I do with it next? Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers
