Lele
I am sorry if I sounded grumpy and demanding. This was not what I intended,
but I see that it has come out like that. Fact is, I *am* glad and thankful
for the work you did with tailor. Without tailor I would never have had the
opportunity to establish Darcs at where I work. And, BTW, I would not care
to write long messages to this list if I wasn't a very dedicated fan of
Darcs, and also very glad that it keeps getting better and better, thanks
to the good work of all you people here. So, all of you, please accept a
big, huge
Thank you!
It was *not* my goal to criticise you personally or diminish the work you
did with tailor. I can perfectly understand if you cannot support it any
longer, or at least not in the way you used to. Nevertheless, it is a fact
that must be taken into consideration.
What I wanted to achieve is bring the problem to the attention of the Darcs
development team. In the past, whenever someone asked about a tool to
convert some foreign repo to Darcs, he/she was told to use tailor. Most of
the other VCSes have more or less tightly integrated tools to convert other
repository formats into their own. Darcs used to have tailor, but if tailor
is starting to suffer from bit-rot then the whole Darcs community has a
problem, as this will make it very hard to get more users, and as a result
people will loose interest.
Now, as you indicated in your answer, tailor was never designed with the
primary goal of supporting migration to Darcs, right? It was designed as a
tool for general VCS to VCS conversion *and* simultaneous one- or
bi-directional cooperation between VCSes. This is much more than what Darcs
needs to offer smooth migration. I would love to see someone take over
development of tailor, but in order to fix the immediate problem something
simpler would suffice and be less work to maintain. I mean, something that
is specialized to the X-to-Darcs conversion task.
I would really like to offer to take over maintenance of the
darcs-fast-import script, as it looks as if this format is going to be the
de-facto standard for repository interchange. With a robust and
feature-complete darcs-fast-import we could cover most of the demands for
easy migration to Darcs. However, I just took over maintenance of another
open source project and I fear this will be more than I can take on,
especially since I am not very versed in Python.
If it appears that all I can do is criticise and not help make things
better, well, I am sorry but I can't help it (except to shut up, which is
what I am going to do now ;-).
Cheers
Ben
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
