Comment 7 for bug 377519

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote : Re: [Bug 377519] Re: Stacked on location breaks if the stacked upon branch is renamed

Jonathan Lange wrote:
> On Mon, Nov 2, 2009 at 8:45 PM, Tim Penhey <email address hidden> wrote:
>> On Mon, 02 Nov 2009 18:53:02 Andrew Bennetts wrote:
>>> An alternative fix would be for Launchpad's code hosting server to store
>>> the immutable database ID rather than the mutable string in the
>>> branch.conf file. This would require intercepting reads and writes to
>>> that file to transparently rewrite that setting (similar to how paths are
>>> translated on the fly when resolving paths to files/dirs on disk), and of
>>> course migrating the existing files. This would have the advantage of
>>> working instantaneously, and it would not require changing a potentially
>>> large number of stacked branches in reaction to a single branch renaming.
>> Andrew, any help you could offer with regard to this solution would be awesome.
>> AFAIK the reason that we didn't do this is that we didn't know how to do it.
>>
>
> Actually we talked about it and decided that it would be really
> frikkin hard. Times change though.

It wouldn't be *that* hard I think. Work, yes, but nothing impossible.
 Would be lots easier if we didn't have to worry about vfs-level branch
access I guess :-)

Cheers,
mwh