#149: a "copy and rm" from svn became an rm when it probably should have become
an mv
---------------------+------------------------------------------------------
Reporter: zooko | Owner: lele
Type: defect | Status: new
Priority: major | Milestone: VersionOne
Component: tailor | Version: 0.9
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment(by lele):
I confirm that, and it seems related to [http://bugs.darcs.net/issue803 a
darcs 2.0 issue].
Since darcs handles the resulting patch without any problem, I'm afraid
the issue won't be fixed (soon). In that case, we can either ''accept''
the status quo, or go down the dirty path of moving back the renamed
thingie and let darcs move it (IIRC bzr or hg backends must do the
same...)
OTOH, what kind of ''real'' problem does this cause? I already met the
same issue, reported by a trac-darcs user, and now the plugin tries to
"filter out" such redundancy, and at least it does not fail if it's not
able to clear the mess but logs a WARNING.
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/149#comment:1>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
