From: "Mike Ralphson" <mike.ralphson@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Boyd Lynn Gerber" <gerberb@zenez.com>,
"Git List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: Bug/problem with 1.6.0 on UnixWare
Date: Fri, 22 Aug 2008 08:58:39 +0100 [thread overview]
Message-ID: <e2b179460808220058o24f9b15bo74c2abcdd70abaab@mail.gmail.com> (raw)
In-Reply-To: <20080821204522.GA29361@coredump.intra.peff.net>
2008/8/21 Jeff King <peff@peff.net>:
> 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.
> 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
prev parent reply other threads:[~2008-08-22 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 11:25 Bug/problem with 1.6.0 on UnixWare Boyd Lynn Gerber
2008-08-21 11:35 ` Mike Ralphson
2008-08-21 12:18 ` Boyd Lynn Gerber
2008-08-21 12:41 ` Mike Ralphson
2008-08-21 13:08 ` Jeff King
2008-08-21 14:38 ` Mike Ralphson
2008-08-21 20:45 ` Jeff King
2008-08-22 7:58 ` Mike Ralphson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2b179460808220058o24f9b15bo74c2abcdd70abaab@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=gerberb@zenez.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).