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, 20:45 UTC
Message-ID
<20080821204522.GA29361@coredump.intra.peff.net>
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.

Show 6 quoted lines
> 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
Previous: Mike RalphsonNext: Mike Ralphson
Message 7 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.