On Thu, 14 Apr 2005, Paul Jackson wrote:
To me, rename is a special case of the more general case of a
big chunk of code (a portion of a file) that was in one place
either being moved or copied to another place.
I wonder if there might be someway to use the tools that biologists use
to analyze DNA
* Paul Jackson <[EMAIL PROTECTED]> wrote:
> Scott wrote:
> > Anyway, maybe it's worth thinking a little about an SCM in which this is a
> > feature, instead of (or in addition to) automatically assuming this is a
> > bug we need to add infrastructure to work around.
>
> Agreed.
>
> To me, the
Scott wrote:
> Anyway, maybe it's worth thinking a little about an SCM in which this is a
> feature, instead of (or in addition to) automatically assuming this is a
> bug we need to add infrastructure to work around.
Agreed.
To me, the main purpose in tracking renames is to obtain a deeper
hist
Perhaps our thinking is being clouded by 'how other SCMs do things' ---
do we *really* need extra rename metadata? As Linus pointed out, as long
as a commit is done immediately after a rename (ie before the renamed file
is changed) the tree object contains all the information one needs: you
can
4 matches
Mail list logo
