#141: API and description for adding generalized conversions
--------------------------+-------------------------------------------------
Reporter: DGtlRift | Owner: lele
Type: enhancement | Status: new
Priority: minor | Milestone: VersionOne
Component: tailor | Version: 0.9
Resolution: | Keywords:
--------------------------+-------------------------------------------------
Old description:
> We use a propriatary VCS that I am trying to convince my peers to move
> away from. The problem is that there is a lot of history, change sets,
> and branches that would need to be converted, and there is no tool that
> exists to convert from this "home-grown" system.
>
> If there was a generalized API with extensive documentation that
> described how to retrieve a change set, mitigate changeset, merge,
> checkin, checkout, brach, etc, so that tailer could then use these
> callouts to push or pull changes between an unsupported VCS and one of
> the built in.
>
> As a first step, it could define the callouts that pull change sets. As
> a second it could then define push callouts to allow generalized
> conversions between two unsupported VCSs.
New description:
We use a proprietary VCS that I am trying to convince my peers to move
away from. The problem is that there is a lot of history, change sets,
and branches that would need to be converted, and there is no tool that
exists to convert from this "home-grown" system.
If there was a generalized API with extensive documentation that described
how to retrieve a change set, migrate changeset, merge, checkin, checkout,
branch, etc, so that tailor could then use these callouts to push or pull
changes between an unsupported VCS and one of the built in.
As a first step, it could define the callouts that pull change sets. As a
second it could then define push callouts to allow generalized conversions
between two unsupported VCSs.
--
Comment(by lele):
The source and target interfaces are already pretty well abstracted and
documented, and I bet it's easier to implement at least the source one for
your VCS, rather then implementing another abstracted set of "callouts".
But since you did mention branches, tailor currently does not handle them
(with the exception of darcs as target system, maybe), so that would be
the main problem.
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/141#comment:2>
Tailor <http://progetti.arstecnica.it/tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
