|
1185.1.29
by Robert Collins
merge merge tweaks from aaron, which includes latest .dev |
1 |
*********************** |
2 |
Common changeset format |
|
3 |
*********************** |
|
4 |
||
5 |
It might be useful to have a common changeset format for interchange |
|
6 |
between projects. |
|
7 |
||
8 |
It is not clear that you would be able to capture everything that |
|
9 |
every tool produces, but perhaps a lot could be done. |
|
10 |
||
11 |
Scenarios: (in order of difficulty?) |
|
12 |
||
13 |
* dump/load |
|
14 |
||
15 |
* convert repo from one tool to another |
|
16 |
||
17 |
* one-way sync from exotic tool into read-only CVS or Svn repo |
|
18 |
||
19 |
* two way sync between writable archives |
|
20 |
||
21 |
Perforce's RevML and ``vcp`` may be some use but apparently don't go |
|
22 |
all the way. |
|
23 |
||
24 |
Things like darcs and monotone may have such a different model that it |
|
25 |
may be hard to map them. |
|
26 |
||
27 |
Two-way sync may require keeping external state and is probably pretty |
|
28 |
hard. |
|
29 |
||
30 |
Apparently tlord tried to do something about this before but it |
|
31 |
stalled. |
|
32 |
||
33 |
Eventually perhaps we could arrange for someone to export key |
|
34 |
bitkeeper archives in this format, allowing all tools to read them in. |
|
35 |
||
36 |
Colin__ points the existing mailing list about this which is just a |
|
37 |
bunch of spam. |
|
38 |
||
39 |
__ http://web.verbum.org/blog/freesoftware/fsrc-responses |