Dear diary, on Sun, Jul 02, 2006 at 11:33:47PM CEST, I got a letter
where Junio C Hamano <junkio@xxxxxxx> said that...
> I tried this:
>
> 0. check out the branch that has the Perly git ("pu"). build
> and install normally to have a perfectly working version
> accessible on your usual $PATH.
>
> 1. apply the patch [1] below to make it use "use lib" instead of
> "unshift".
>
> 2. break perl/Git.pm being built to pretend we introduced a bug
> in the work in progress by applying the patch [2] below.
>
> 3. without installing the broken Git.pm, run "make test", and
> see a test that uses "git pull" and needs to create a true
> merge succeed. It tells me that everything including
> perl/Git.pm is GOOD, and I'd find the breakage only after
> installing and running the test again.
So, just to clarify and make sure we understand each other perfectly,
you claim that when skipping (1), (3) _does_ FAIL for you? Because it
really doesn't for me and I can't see how could it ever fail without
installing the broken version first.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html