Daniel Freedman wrote:
Hi Lele,
I've just started experimenting with Tailor, and I think it's
wonderful. I'm quite grateful for what you've managed to accomplish
here...
Thank you!
1. On import of the cvs tree into darcs, the tags appear to have the
wrong date/time and lose the metadata on the committer (who is
listed as "Unknown tagger."). Specifically, rather than having the
date-time correctly set as the rest of the patches from that tree
do, the tags have the current date/time in darcs.
Yes, I know; the tag handling was a contribute and I never had the needs
to fully understand it ;-)
I created ticket #104...
2. I've also experimented with the most recent version of tailor
... and #105
3. A further issue with 0.9.27+ compared to 0.9.26 is that, when fed
... and #106
4. I recall something from the first few times I played with tailor,
but haven't been able to find since then. After the conversion
from cvs to darcs, I viewed the changesets or something (can't even
remember at this time) and found an initial entry which was listed
as the "tailorization" and also had the user and even the
fully-qualified domain name on which it was performed. However, I
can no longer find this info or recall where it came from, though
I've looked with 'darcs changes' and 'darcs annotate'... Can you
imagine where it might have been or what I might have been thinking
of?
The "tailorization" patch happens to be the very first one in the target
repository *when* tailor starts from a source revision other than the
INITIAL one (that is, when it starts from a "snapshot" of the source at
an arbitrary point in time).
5. A feature request: Might it be possible to permit a mapping of the
committer upon VCS conversion.
That's very easy, see the first example of the section "Pre-commit and
post-commit hooks" in the README.
6. I think it would be beneficial to clarify further what I consider
one of the more potentially confusing aspects of tailor configuration.
Yep, patches are welcome!
> 7. I think it would be beneficial to more clearly explicate that darcs
1.0.2 doesn't properly work with tailor, as it is still the default
for Debian sarge/stable (I had to use 1.0.8 from sarge-backports).
It isn't really clearly mentioned in the docs (only briefly stated
in the README), and it largely works, which make determination of
its failures more difficult. The only failure I personally
recognized was that it didn't properly import tags from cvs into
darcs.
Will update/expand a little the annotation, but what isn't clear enough in
.. [#] Darcs 1.0.2 is too old, 1.0.3 is good, 1.0.4 (the fourth
release candidate is under final testing) is recommended since
it's faster in most operations!
?
8. I couldn't find any mention in the documentation that subversion
1.2+ is required to work with some of the tailor defaults (and,
again, subversion 1.1.4 is default in Debian sarge), namely
'--limit' and '--ignore-externals'. Granted that both of these can
be disabled via tailor configuration options, but the need to do so
(or to use a certain baseline subversion) should probably be
clarified in the README.
Right, will do.
Once more, thanks to you and the rest of the tailor team for a great
piece of software. I appreciate all you do. Please let me know if
you need any further information from me to help diagnose any of the
above.
Thank you again. Unfortunately the "tailor team" does not have the
resources to fix the growing list of unresolved tickets. Luckily (err,
not for me...) I will *have* to find some time to spend on it RSN, as in
the last couple of days I had a some tailorization failures (I keep
dozens of "darcsified" repositories with tailor), and that is
untollerable for me :-)
bye, lele.
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
