git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 21 Aug 2008 15:38:32 +0100	[thread overview]
Message-ID: <e2b179460808210738y9ca6e3fka113128fb1e6e024@mail.gmail.com> (raw)
In-Reply-To: <20080821130816.GB22453@coredump.intra.peff.net>

2008/8/21 Jeff King <peff@peff.net>:
> On Thu, Aug 21, 2008 at 01:41:07PM +0100, Mike Ralphson wrote:
>
>> You're very welcome to push tags describing the state of the build and
>> tests to http://repo.or.cz/w/git/gitbuild.git
>
> BTW, on my todo list is pushing my tags there. I am building FreeBSD
> nightly, and I plan to add Solaris 2.8. I just haven't gotten around to
> making the build work yet...:)

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!

>> Personally, I'd like it if Junio could check to see if the 'satellite'
>> platforms are happily building and passing the last rc before he tags
>> a final release (with no additional code changes in it!), but that may
>> be too much of the tail wagging the dog.
>
> I think his procedure is more reactive. He tags 1.6.0-rc*, and he
> expects us to complain to him if it is broken.

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.

Mike

  reply	other threads:[~2008-08-21 14:40 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 [this message]
2008-08-21 20:45           ` Jeff King
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=e2b179460808210738y9ca6e3fka113128fb1e6e024@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).