Re: [PATCH] cvsimport: rewrite to use cvsps 3.x to fix major bugs
- From
Michael Haggerty <mhagger@alum.mit.edu>
- Date
- Jan 14, 2013, 05:12 UTC
- Message-ID
- <50F393D6.2010603@alum.mit.edu>
- In-Reply-To
- <7v8v7wiv3a.fsf@alter.siamese.dyndns.org>
On 01/13/2013 11:20 PM, Junio C Hamano wrote:
> After a quick survey of various distros, I think it is very unlikely > that we will see "distros move on to newer cvsps, leaving cvsimport > broken" situation. If anything, it is more like "distros decide to > ignore the new cvsps, until it is made to work with cvsimport" [*1*].
A better predictor of the distros' decisions is probably which other packages depend on cvsps. As one data point: on Debian squeeze and on Ubuntu precise, only two packages depend on cvsps (git-cvs and bzr-cvsps-import) and one suggests it (chora2, "a code repository viewing component for horde framework"). So also by this standard they are unlikely to feel a lot of pressure to update quickly to cvsps3.
> I think it is probably sensible to [...] > > Agreed?
Yes, I agree that what you propose is a good strategy.
Michael
-- Michael Haggerty mhagger@alum.mit.edu http://softwareswirl.blogspot.com/