git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug/problem with 1.6.0 on UnixWare

From
Jeff King <peff@peff.net>
Date
Aug 21, 2008, 13:08 UTC
Message-ID
<20080821130816.GB22453@coredump.intra.peff.net>
In-Reply-To
<e2b179460808210541lfd7dcaeoea8554a2a76f8825@mail.gmail.com>
On Thu, Aug 21, 2008 at 01:41:07PM +0100, Mike Ralphson wrote:
Show 5 quoted lines
> If it's possible, you might want to look at automatically building and
> running the git testsuite on some or all of your SCO etc platforms.
> You're very welcome to push tags describing the state of the build and
> tests to http://repo.or.cz/w/git/gitbuild.git - there's a few scripts
> there in a side branch.

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...:)

> 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. The real deficiency here is that the broken platforms were not tested.

-Peff
Previous: Mike RalphsonNext: Mike Ralphson
Message 5 of 8 in “Bug/problem with 1.6.0 on UnixWare”
  1. Boyd Lynn GerberAug 21, 2008
  2. Mike RalphsonAug 21, 2008
  3. Boyd Lynn GerberAug 21, 2008
  4. Mike RalphsonAug 21, 2008
  5. Jeff KingAug 21, 2008
  6. Mike RalphsonAug 21, 2008
  7. Jeff KingAug 21, 2008
  8. Mike RalphsonAug 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.