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

RE: Re: svn commit: rev 1957 - trunk/subversion/include trunk/subversion/libsvn_wc

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-05-17 03:21:58 CEST

> From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
> <peter.westlake@arm.com> writes:
> > I don't agree that this is what modules should be about. If the FS
> doesn't
> > know about modules, how can SVN answer questions about them? For
> instance,
> > "what changed in this module between revs A and B?". If you're using
> > modules
> > to gather source for product that you're going to build, that's an
> > important
> > question to be able to answer. Modules are (IMO, naturally) all
> > sharing
> > source. That's definitely a source control function.
> Non-problem. They are versioned, as described in issue #517.
> I don't really understand your question, I guess: "If the FS doesn't
> know about modules, how can SVN answer questions about them?"
> Answer: "In the manner described in issue #517, among other ways." :-)

Err, that's not quite what I think he means.

I think his question is more like this:
"If the FS doesn't know about modules in a formal schema way, then how
can the FS deliver answers to arbitrary queries about modules, their
usages, and any other odd fact you'd want to find out about modules?"

i.e. If the FS actually had a SQL store and modules were stored the way
you suggested then you couldn't possibly write a SQL query (or stored
procedure) that reasoned about modules in any decently easy way, form,
or fashion.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 17 03:23:01 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.