Re: Let's stop using CVS for debian.org website

在 2016年11月20日星期日 SGT 下午12:08:04，您写道：
> For what it's worth, there's also git-cvsimport(1) and
> git-cvsexportcommit(1) that can be used if someone really wants to
> contribute and doesn't want to touch cvs itself.

Sure. I tried git-cvsimport to convert the cvs repo into a git repo (with -r 
option enabled and -A disabled). The whole process took ~60 hours and the final 
git bare repo is ~260MiB large.

I also found that the process is incremental after the initial import as long 
as the history is not modified, which is a really good news for those who wants 
to work on the transition.

I think we can make a smooth transition through the following process:

* open a git repository under the webwml alioth team, make an initial import.
* set up a crontab job somewhere (e.g., directly on alioth.d.o) and sync from 
the cvs repository to git repository several times every day. Incremental 
update is easy and can be finished within 10 minutes every time we sync them.
* gradually port all potential infrastructures (e.g., tools used to update 
debian.org website) from cvs repository to git repository.
* set up a "transition day". After that given day, all the commits have to go 
into the git repository. Done.

What do you think?


--
Sincerely,
Boyuan Yang

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEBxWNsAe8FiJWLc/BsaNiERUBsx4FAlgyrZcACgkQsaNiERUB
sx4Xvw//e+welflCFReyEQeR0WsrqZ2aJl8SX/ATDlR+cbfMuK37uROGbt9ciq5H
SbVOsuBOMxV5yrq7xLu2JGH4i9evIa+2qP3bacEsxGOrz/9cE9QeVKXp57ZNnUY0
XzrPM2PVhfkQ7YPN/XODLYKHF1Sf5MN4YAxBRdOiAGE/gumxIf7X4vZtW96m84jc
m+Tg3vu+vkqpXdHKM+mcTsGYC8OQBIOjS2AQxMXCVuDw5pZp4sbxbKZpGDZcg3Ju
4yd4VDrVKRXlUMiywPNAeObHlDv03Ynlyz6Kjn5L6yib/Mk49Rbq/IwvL2dPVhzV
WgFUVQKbOQdwR3zOC7aPdBbWDPmsJWCc8K0h+XNNCwSK+TJiysGWUvN2tquwWSTF
yd711S7S0PVFIUVZBm1rhCAawodKVQM2SW7v/ViUu6+DFlby8K2dN8NH5glUCVa1
5ukfGrWAy+r029wAdBrI03o3fULqEi00GIP9eg1n694GsPc/t4JxAUWS9TuhjqkT
v58IPgjsuk6nxh2/Ur1NQsLNlVgdegt6NCcvwvp0exM7aT53wVHFUvH9yAqDZt/K
zr23vURin5dc84cohOSgK0dwWJnRAIeeWxKG4HeZBRRJYHJhQUWRc8Biwg1PqvDN
KBpI+k5j573cDy6zlAVGOEKe+df8AIKj7KS1OezQesux7wdZShE=
=KI2Z
-----END PGP SIGNATURE-----