Re: Tagline tagging failings -- Was: Re: [Gnu-arch-users] tla mv gets me an error next commit

[Miles Bader]

"Karl O. Pinc" <address@hidden> writes:
>> As I described in my earlier message, it seems perfectly possible to
>> do the job efficiently without any such "keeping records", and
>> desirable to do so, as such record-keeping has a number of fairly
>> severe problems[*].
>
> It's not like I know what I'm talking about here, but I've doubts
> about your statement.  Because if it's _really_ possible to do the
> job without "keeping records" then there would be no need for
> explicit tagging _ever_, and arch wouldn't have it.

No, that's incorrect.

Explicit tags are _exactly_ like taglines:  they describe an absolute
piece of state in the source tree, a file-name-to-id association.

"Keeping track" of mv/rm/add would _not_ be "absolute" -- it records a
_change_.  Recording changes to a dynamic source tree is problematic
your records only makes sense in a particular context, and so you must
be very careful to make sure it is kept up to date with respect to any
further changes -- some of which may happen outside your control.

> I'm not impressed with taglines, for reasons given in a previous email.
> I'm not asking everybody to give up taglines, I'm asking everybody
> who uses taglines to give up on fixing the partial commit problem.

Ok; now that I've explained why you're wrong, can you please stop asking
this?

-Miles
-- 
The secret to creativity is knowing how to hide your sources.
  --Albert Einstein