[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] [BUG] FEATURE PLANS: relink
From: |
David Allouche |
Subject: |
Re: [Gnu-arch-users] [BUG] FEATURE PLANS: relink |
Date: |
Sun, 30 May 2004 20:49:50 +0200 |
User-agent: |
Mutt/1.5.5.1+cvs20040105i |
On Tue, May 25, 2004 at 10:22:20AM -0700, Tom Lord wrote:
>
> > From: Aaron Bentley <address@hidden>
>
> > Tom Lord wrote:
> > > % tla relink
>
> > > Attempt to ensure the existence of a library revision
> > > for the immediate ancestor of the current project tree.
>
> > > Print a list of files modified, added, and deleted.
>
> > > Attempt to ensure that all non-modified files are
> > > hard-links to the library revision.
>
> > Since this seems to be just "tla changes --link", could you explain the
> > difference?
>
> Heh. Mostly it's that I forget `changes --link' exists but `relink'
> is intended to do something slightly different, anyway: to not bother
> computing a full changeset between the two trees -- just the lists of
> deleted, added, and modified files.
(pyarch maintainer on)
So, what is the status of "changes --link", is it planned for
deprecation?
It feels like relinking should really be supported only as
arch.WorkingTree.relink and not at all as an option to
arch.WorkingTree.changes.
Requesting blessing.
--
-- ddaa