Makes sense to me. On Thu, 2011-02-17 at 08:49 -0700, Barrett, Brian W wrote: > Why did "we" make this change? It was originally this way, and we changed it > to the no-auth way for a reason. > > Brian > > > ----- Original Message ----- > From: Jeff Squyres [mailto:jsquy...@cisco.com] > Sent: Wednesday, February 16, 2011 09:24 AM > To: Open Developers <de...@open-mpi.org> > Subject: [OMPI devel] Minor OMPI SVN configuration change > > We have made a minor change in OMPI's SVN configuration: > > If you access the SVN repo over https, you *must* authenticate. > > Previously, you could authenticate or not; SVN would serve up what was > appropriate in either case (there's one "private" tree in the SVN repo for > not-yet-published academic work). > > Anonymous, read-only access to SVN is still provided over http. > > I doubt that this change will affect most people, because most people check > out via https only if they plan to commit -- meaning that they have a > write-enabled SVN account. > > Let me know if you have any questions / problems with this change. > --
Kenneth A. Lloyd Director of Systems Science Watt Systems Technologies Inc. Albuquerque, NM USA kenneth.ll...@wattsys.com
