[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: fsfs and user permissions

From: <kfogel_at_collab.net>
Date: 2005-04-13 18:54:02 CEST

Alvin Thompson <alvin-svn@thompsonlogic.com> writes:
> kfogel@collab.net wrote:
> > Plenty of users have that knowledge -- a question like this should go
> > to users@, since it's not about Subversion development.
>
> i was just trying show that i considered sending to users before i
> sent here, so i wouldn't get flamed. ;)

We don't flame based on what you think, but on what you do :-).

(But don't worry, you're not going to get flamed anyway.)

> the reason i asked here is because i want more of an 'authoritative'
> answer than an 'anecdotal' one. anecdotally (is that a word?), i
> already know this approach works and i expect i'd get the same answer
> in the user list, since there have been wiki's/web pages describing
> this process.
>
> however, the 'dev' list (i assume) would have more knowledge of issues
> that affect actual operation. for example, i remember there was a bug
> in 1.2 where if the 'db/format' file was outdated or missing, *all*
> operations would attempt to write to the repository and thereby break
> things if the repository were read-only. i'm not sure that most users
> are aware of this kind of technical stuff, so i ask here.
>
> to use a (bad) metaphor, every crow i've ever seen is black. while i
> could probably safely assume that *all* crows are black, i'd feel a
> lot better logically or scientifically proving it, if something
> important (like my code) depended on it.
>
> so i probably should have worded my question to say, "is anyone aware
> of any issues that would prevent things from working this way?"

The dev@ list is for development discussion. It's not simply the next
level of support escalation after users@.

When we forward threads from users@ to here, we do it because we think
the thread has potential to reveal a bug we need to know about, or for
some other reason that will contribute to Subversion's development.
If the user happens to get helped as a result of that, that's a nice
side effect, but it's not what the dev@ list is for.

Hope this clarifies,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 13 19:22:19 2005

This is an archived mail posted to the Subversion Dev mailing list.