From: Jeff King <peff@peff.net>
To: Mike Ralphson <mike.ralphson@gmail.com>
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: Thu, 21 Aug 2008 16:45:22 -0400 [thread overview]
Message-ID: <20080821204522.GA29361@coredump.intra.peff.net> (raw)
In-Reply-To: <e2b179460808210738y9ca6e3fka113128fb1e6e024@mail.gmail.com>
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.
> Granted, but Junio seems to do releases at the weekend, and sometimes
> they aren't the same content as the previous rc. Though I build and
> test 7 days a week, I'd rarely look at the test results over the
> weekend. And I was on vacation when the last minute AIX breakage went
> into 1.5.6 - not that I would necessarily have been able to fix that
> one.
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.
-Peff
next prev parent reply other threads:[~2008-08-21 20:46 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 [this message]
2008-08-22 7:58 ` Mike Ralphson
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=20080821204522.GA29361@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=gerberb@zenez.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mike.ralphson@gmail.com \
/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).