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

Re: FSFS successor ID design draft

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Fri, 26 Aug 2011 16:51:51 +0400

On Fri, Aug 26, 2011 at 16:49, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> On 08/26/2011 08:32 AM, Ivan Zhakov wrote:
>> On Fri, Aug 26, 2011 at 15:14, Stefan Sperling <stsp_at_elego.de> wrote:
>>> Below is an initial draft of a design for successor-IDs in FSFS.
>>> It is a bit long, but I hope it covers all relevant points in
>>> sufficient detail.
>>> Please share your thoughts on this. I have most likely missed a few things.
>>> If we like it I will put it into the repository for further editing,
>>> either in notes/ on trunk or onto the fsfs-successor ID branch.
>>> If this design has some severe problem I don't mind going back to
>>> the drawing board. This is my first shot, afterall :)
>> Hi Stefan,
>> I've may be stupid question: what is the purpose of storing
>> fsfs-successor ID? Do we need them for proper handling of
>> moves/renames or for something else?
> We need them for forward-direction history searching, move handing, and
> answering the top-ten enterprise question "I fixed this bug HERE, but in
> what other branches does the same bug exist?"
Mike, thanks for the answer, but I still don't understand how
successor ID information could help us with move handling?

Ivan Zhakov
Received on 2011-08-26 14:52:44 CEST

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.