Junio C Hamano gits...@pobox.com writes:
Jonathan Nieder jrnie...@gmail.com writes:
Michael Haggerty wrote:
Regarding your claim that within a few months the Perl git-cvsimport is
going to cease even pretending to work: It might be that the old
git-cvsimport will stop working *for people
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
On 01/11/2013 04:32 AM, Junio C Hamano wrote:
From: Eric S. Raymond e...@thyrsus.com
The combination of git-cvsimport and cvsps had serious problems.
Agreed.
[...]
This patch also removes Michael Haggerty's git-cvsimport tests
(t960[123]) from the git tree. These are actually
Junio C Hamano gits...@pobox.com:
And here is what I got:
Hm. In my version of these tests, I only have one regression from the
old combo (in the pathological tags test, t9602). You're seeing more
breakage than that, obviously.
A funny thing was that without cvsps-3.7 on $PATH (which means I
Michael Haggerty mhag...@alum.mit.edu:
Otherwise, how do we know that cvsps currently works with git-cvsimport?
(OK, you claim that it does, but in the next breath you admit that
there is a new failure in one pathological tagging case.) How can we
understand its strengths/weaknesses? How can
Hi Eric,
Eric S. Raymond wrote:
But in practice the git crew was going to lose that
capability anyway simply because the new wrapper will support three
engines rather than just one. It's not practical for the git tests to
handle that many variant external dependencies.
See the
Michael Haggerty wrote:
Regarding your claim that within a few months the Perl git-cvsimport is
going to cease even pretending to work: It might be that the old
git-cvsimport will stop working *for people who upgrade to cvsps 3.x*.
But it is not realistic to expect people to synchronize their
From: Eric S. Raymond e...@thyrsus.com
...
diff --git a/git-cvsimport.perl b/git-cvsimport-fallback.perl
similarity index 98%
rename from git-cvsimport.perl
rename to git-cvsimport-fallback.perl
index 0a31ebd..4bc0717 100755
--- a/git-cvsimport.perl
+++ b/git-cvsimport-fallback.perl
@@
Eric S. Raymond e...@thyrsus.com writes:
Junio C Hamano gits...@pobox.com:
I think the prevalent style in this script is to write print
without parentheses:
print STDERR msg\n;
That can be easily fixed.
This looks lazy and unsafe quoting. Is there anything that makes
sure
Eric S. Raymond e...@thyrsus.com writes:
Junio C Hamano gits...@pobox.com:
...
The other is a design-level problem - these options were a bad idea to
begin with. In earlier list mail I said
An example of the batchiness mistake close to home is the -m and -M
options in the old
I cloned git://gitorious.org/cvsps/cvsps.git and installed cvsps-3.7
at c2ce6cc (More fun with test loads, sigh. Timezones suck.,
2013-01-09) earlier on my $PATH, and tried to run t96xx series with
this patch applied on top of Git 1.8.1.
The first thing I noticed was that all the tests were
From: Eric S. Raymond e...@thyrsus.com
The combination of git-cvsimport and cvsps had serious problems.
Among these were:
(1) Analysis of branchy repos was buggy in multiple ways in both
programs, leading to incorrect repo translations.
(2) Even after a correct branch analysis, extra
12 matches
Mail list logo
