Re: [Gnu-arch-users] GNU Arch review - am I accurate?

[Jan Hudec]

On Sun, Mar 07, 2004 at 21:15:40 +0000, David A. Wheeler wrote:
> Andrew Suffield said:
> > > The mirroring capability is clever, but if you download a mirror and
> > > make a change, you can't commit the change and the tool isn't smart
> > > enough to help.
> > 
> > I can't see that there's anything it could or should do. tag, then
> > commit - it's not complicated. Using undo here is a daft idea.
> 
> But if you've acquired stuff from a mirror, as long as the mirror
> is up-to-date there's no reason that commit should cause a problem.
> Tla should be able to find the 'real' archive and commit instead.
> 
> My evidence is at:
> http://wiki.gnuarch.org/moin.cgi/Arch_20Recipes#head-2c5332402d44ef87a1bb8d4fdf2ccaf758a57334
> 
> Where it says:
> "Say for example that you tla get a source tree from an archive mirror, and 
> start
> hacking on it. After you have made a bunch of changes, you realise that you 
> cannot
> commit the changes back, as the originating archive was a mirror. You really 
> should
> have created a new branch to commit the changes on. You can use the command 
> tla
> undo to revert the tree back to its original revision, and save the changeset.
> You can then move this changeset elsewhere, make a branch (or whatever fixup 
> is
> required). Then you use the tla redo command to reapply the changes to the
> new source tree, after which you can commit."

Hell now THIS I call COMPLICATED!

Just:
    aba branch-this <new-branch-name>
If you have the tla-contrib. Anyway, the command is just:
    tla tag -S $(tla logs -r -f | head -n 1) <new-branch-name>
    tla sync-tree <new-branch-name>--base-0
    tla set-tree-version <new-branch-name>

Definitely no reason to undo, move or anything like that.

-------------------------------------------------------------------------------
                                                 Jan 'Bulb' Hudec 
<address@hidden>

signature.asc
Description: Digital signature