Re: [Monotone-devel] Tailor

[rghetta]

Nathaniel Smith wrote:
> On Wed, Oct 11, 2006 at 10:11:28PM +0200, rghetta wrote:
> > Tailor limitations aside, Brian's log reports a rename from statistics 
> > to statistics/squid which imho just doesn't make sense (and monotone 
> > obviously complaints).
>
> A rename like that makes perfect sense... the question is how to
> convince tailor to present it sensibly.
Sorry, I've lost you. The source scm says: rename statistics to 
statistics/squid. Do you mean it should be interpreted as rename stats 
to temp, create dir stats, rename temp to stats/squid ?
Tailor sure doesn't do anything like that. Given the differences in 
rename support among scms, I doubt Tailor could do this sort of 
inference in a scm-independent way.
Perhaps the monotone backend could be enhanced to work this way, however.

> But foo/ might have disappeared because it was renamed, rather than
> because it was deleted :-).
Perhaps my explanation wasn't very accurate, sorry. Tailor build its 
change list by parsing the output of a source scm command (like log or 
diff), not by comparing the wc content before and after the update.
Tailor usually doesn't do anything file/directory related. All 
file-level operations are carried by the source or target scm.
So if foo/ doesn't exists anymore, the source scm should report that in 
the change list (as rename or deletion, whichever applies).
If foo/ becomes bar/ and the change list contains "add foo/a" it refers 
to a new foo/, otherwise the change list must be "add bar/a".

Riccardo