Re: Bug/problem with 1.6.0 on UnixWare

From: Mike Ralphson <mike.ralphson@gmail.com>
Date: Aug 21, 2008, 12:41 UTC
Message-ID: <e2b179460808210541lfd7dcaeoea8554a2a76f8825@mail.gmail.com>
In-Reply-To: <alpine.LNX.1.10.0808210610440.29396@xenau.zenez.com>

2008/8/21 Boyd Lynn Gerber <gerberb@zenez.com>:

Show 13 quoted lines

> Yep, that sounds about right.  It has bitten me on the 12 platforms, I
> submitted to get git working on them.  I will look at reverting it.
>
> I just tried to get this working and now I am being flooded with emails
> from people that are trying git for the first time, and asking...
>
> How I could your recommend such a broken SCM?  I told them to got back to
> the 1.5.X but being new to git and then not being able to build and use it
> is causing a lot of flack.  I am getting emails now about my recommending
> git, as it is broken.  I should not have announce to the various lists
> about how great git is and that they should dump their older SCM's in
> favor of git.  Really bad timing on my part.  I just hope these people
> will give git an other try.

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.

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.

Even though 1.6 builds and passes here, I probably won't push it out in my environment until 1.6.0.2 or so.

Mike