On 5/16/2016 11:41 AM, John P. Rouillard wrote:
> Richard Hipp writes:
>> On 5/15/16, Andy Goth <andrew.m.g...@gmail.com> wrote:
>>>
>>> To fix, you're going to have to go back to the version prior to the shun
>>> and redo every check-in since that point.
>>
>> Another option is to "reparent" the first check-in after the shun such
>> that it's parent becomes the last check-in before the shun.  There is
>> a "parent" tag for this purpose.
> 
> That is what I was hoping for. Is there any documentation on the
> parent tag? A full text search of "parent NEAR tag" returns too many hits
> and none of the documentaion hits seem to apply.

I've wanted reparenting capability to support importing old history into
a Fossil repository.

For example, I'm given a snapshot of version 2 of a software system and
am told to use it as my baseline.  I make it be the initial import of a
new Fossil repository, then I do my thing.  But then I have questions
about history, and someone gives me a snapshot of version 1.  I want to
import that so I can do diffs and other things through the Fossil
interface, but I can't without recreating the repository using pretty
much the same technique I outlined in my first reply to this thread.

Another scenario would be me being given CVS, SVN, RCS, Git, or other
history data some time after initially creating my repository from one
or a small number of snapshot versions.  I can import these
incrementally, but I can't retroactively integrate what's imported with
the timeline, only keep it in a branch off to the side.

If I can check in control artifacts to facilitate stitching these
otherwise disparate timelines together, then I'll be able to sanely
manage situations such as the above, as well as fix the hole caused by
shunning a non-leaf check-in.

-- 
Andy Goth | <andrew.m.goth/at/gmail/dot/com>

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to