[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] Re: [PATCH] Re: bazaar bug #385 (Re: Stabilizing Bazaar
From: |
Robert Widhopf-Fenk |
Subject: |
[Gnu-arch-users] Re: [PATCH] Re: bazaar bug #385 (Re: Stabilizing Bazaar?) |
Date: |
Wed, 6 Jul 2005 22:48:17 +0200 |
On Monday, July 4, 2005 at 23:24:45, Matthieu Moy wrote:
> Robert Widhopf-Fenk <address@hidden> writes:
>
> > My problem comes from a call to arch_archive_connect_branch
> > within arch_build_revision. It was called for an archive
> > which I did not register and thus returned NULL.
>
> Then, it was not a real "bug", but a bad error message.
>
> I've just comitted a patch to issue an explicit error message in
> your case, and "exit(2)".
>
> Is it OK?
No, IMHI it IS a bug.
Merging from archive A must NOT require access to archive B.
While baz might use B to find a better merge point/strategy
it must not require access to B, since this effectively prevents
merging from A when B is gone.
B might be gone without being able to get access to it again.
Baz should give a warning (about suboptimal merging?), but
it still should be able to merge from A. Tla is able to do
so and IMHO it is a must for a distributed SCM.
Cheers Robert
[Gnu-arch-users] Re: [PATCH] Re: bazaar bug #385 (Re: Stabilizing Bazaar?), Matthieu Moy, 2005/07/09