Re: cvsimport still not working with cvsnt
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 22, 2011, 23:08 UTC
- Message-ID
- <7vipwbbrcc.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <7vtyfxgdz2.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 5 quoted lines
> It is probably unlikely to see a SP in the pathname, but I do not think it > is reasonable to introduce a regression to forbid '=' in the pathname to > the repository, which we have been supporting since August 2009, when we > know the patch as-is will regress the use case, and especially when we > already know a way to code not to regress is not too complex.
Even though I don't deeply care about what CVSNT does, but I am somewhat curious why this "change SP to =" was done when CVSNT writes out its $HOME/.cvs/cvspass file.
Does anybody know why? Only to make things incompatible, perhaps? ;-)
http://www.selenic.com/pipermail/mercurial/2009-April/025095.html
seems to indicate that somebody next door had a similar experience on exactly the same issue.