On 3/30/07, Andrew Bennetts <email address hidden> wrote:
> I agree with John: once the smart server has enough smart verbs this
> will be solved properly, but until then we should try warn users of "bzr
> serve" when it's not going to do what they expect.
I agree too.
One easy way to fix this may be: if we're trying to open the branch at
a url and we find a branch, but looking upwards we hit the root before
finding the repository, then we should maybe give a more specific
error. That will at least make it clear that there is a branch there,
but we couldn't open its repository.
Even after we don't need vfs access to the repository we need to
consider cases like
On 3/30/07, Andrew Bennetts <email address hidden> wrote:
> I agree with John: once the smart server has enough smart verbs this
> will be solved properly, but until then we should try warn users of "bzr
> serve" when it's not going to do what they expect.
I agree too.
One easy way to fix this may be: if we're trying to open the branch at
a url and we find a branch, but looking upwards we hit the root before
finding the repository, then we should maybe give a more specific
error. That will at least make it clear that there is a branch there,
but we couldn't open its repository.
Even after we don't need vfs access to the repository we need to
consider cases like
cd trunk/bzrlib
bzr serve
(can't do anything)
--
Martin