[openbeos] Re: Protecting 'in progress' folders from anonymous CVS
- From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 10 Sep 2001 11:23:25 -0400
Thanks - I wrote those. :-)
I don't mind keeping them open - if someone wants to read and understand
the code without signing up, all the power in the world to them.
I wouldn't be leary - the way I see it, if I feel good enough about submitting
for review by team members, anyone should be able to see it.
Anyone feel differently?
>Hey Michael...
>
>I've been looking thru the kernel_kit downloaded via anonymous CVS. I
>noticed some text files in the 'docs' directory. Actually, it's pretty
>cool to see these -- nice to know that someone is documenting the
>calls.
>
>However... shouldn't these be hidden from the average joe? Both the
>'docs' and 'test' folders are meant to contain working files that are
>still "in-progress". Don't we want to protect them from being accessed
>by anyone? I think programmers are going to be leary of checking in
>stuff otherwise. Only the 'source' folder, which contains the final,
>"good" version should be viewable by all. The rest should require a
>password.
>
>
- Follow-Ups:
- [openbeos] Re: Protecting 'in progress' folders from anonymous CVS
- From: Erik Jakowatz
- References:
- [openbeos] Protecting 'in progress' folders from anonymous CVS
- From: Daniel Reinhold
Other related posts:
- » [openbeos] Protecting 'in progress' folders from anonymous CVS
- » [openbeos] Re: Protecting 'in progress' folders from anonymous CVS
- » [openbeos] Re: Protecting 'in progress' folders from anonymous CVS
- » [openbeos] Re: Protecting 'in progress' folders from anonymous CVS
- [openbeos] Re: Protecting 'in progress' folders from anonymous CVS
- From: Erik Jakowatz
- [openbeos] Protecting 'in progress' folders from anonymous CVS
- From: Daniel Reinhold