Re: [Gnu-arch-users] tla rescue-tree

[Brian May]

>>>>> "Tez" == Tez Kamihira <address@hidden> writes:


    Tez>     1.) "tla undo" in my working copy(= project tree) to save
    Tez> the last modified changeset to some safety area.

    Tez>     2.) make newly temporaly archive named "a--b-temp--1.0"
    Tez> in _my_ machine (= C) by "tla archive-setup a--b-temp--1.0".

    Tez>     3.) "tla set-tree-version a--b-temp--1.0"

    Tez>     4.) mkdir -p
    Tez> {arch}/a/a--b-temp/a--b-temp--1.0/address@hidden/patch-log

    Tez>     5.) tla import

    Tez>     6.) tla redo

    Tez>     7.) tla commit -L"you can't be more helpful."

    Tez> Network is reachable again. Now I can do

    Tez>     8.) tla update a--b--1.0

    Tez> or

    Tez>     8'.) tla star-merge a--b--1.0 .

    Tez> to get "a--b--1.0--patch-3" and "patch-4".

I have a situation that is different to the a above, but I was hoping
the above steps would help.

Anyway, my situation is as follows:

Suppose I have am working on a private repository (there are many
reasons it could be private; I won't list them here).

I have committed a number of revisions, and then for what ever reason
you want to make one of the directories, but only one directory public
(possibly with the implication that more and more code eventually will
be made public until the entire project is public).

What should I do?

The obvious solution would be to create a branch and then delete the
unwanted files in the branch. This won't work, as deleting the files
will make them all available in the branch.

The method I considered was:

Create new archive using:

1. tla init-tree $public_archive/$public_project
2. Copy public files and associated arch-ids across.
3. Commit.
4. Update and commit.

Copy changes across to private tree using:

1. tla update $public_archive/$public_project
   update: tree has no common history with version

2. tla replay $public_archive/$public_project
   unable to open file "[...]/$public_project--base-0.patches.tar.gz" (No such 
file or directory)

3. tla replay $public_archive/$public_project--patch-1
   worked fine, but reports base-0 patch missing

4. tla star-merge $public_archive/$public_project
   star-merge: unable to merge unrelated trees.

In step 3 above, I wanted replay to ignore base-0, I tried: "tla
add-log-version $public_archive/$public_project--base-0", but get the
error "add-log-version: invalid version name [...]".

I am not yet sure what to do if more of the code in the original
project become public.

Any comments? Is there any sanity to what I am doing, or is this just
"weird"? Are there better ways?

The more I think about it, I wonder if perhaps this is a bad idea, and
I should keep them as separate projects.
-- 
Brian May <address@hidden>