Re: Bug/problem with 1.6.0 on UnixWare

From: Mike Ralphson <mike.ralphson@gmail.com>
Date: Aug 22, 2008, 07:58 UTC
Message-ID: <e2b179460808220058o24f9b15bo74c2abcdd70abaab@mail.gmail.com>
In-Reply-To: <20080821204522.GA29361@coredump.intra.peff.net>

2008/8/21 Jeff King <peff@peff.net>:

Show 7 quoted lines

> On Thu, Aug 21, 2008 at 03:38:32PM +0100, Mike Ralphson wrote:
>
>> Great stuff. Though I think it might provoke some patches to improve
>> the display of multiple long tag names for the same commit in gitweb!
>
> Heh. Can you pass along the final version of your build script? I want
> to make sure we are doing the same things.

http://repo.or.cz/w/git/gitbuild.git?a=blob;f=gitbuild.sh;h=d06fbef3c7aa54ea3beab4b3eed4d73387f3b136;hb=2da51f87b94ef564691a656f91b97472bf6d8c53

The setting of the PATH and GIT_SKIP_TESTS are obviously env. specific.

At the moment there's still a bit of manual faffing around when next is rewound after a release.

Show 5 quoted lines

> Yes, in theory, last minute code changes could cause a portability
> breakage. However, any changes from the last -rc to the release version
> tend to be extremely conservative (as judged by Junio), so in practice
> I don't think it happens. For example, I think this git-shell bug made
> it into master over a month before release.

True, this instance isn't a last minute breakage.

Mike